unix: update to Linux 6.11
DO NOT REVIEW DO NOT SUBMIT
This PR (HEAD: ccac3ed8c0c06943e7a29be311f90d8cb9d0a53d) has been imported to Gerrit for code review.
Please visit Gerrit at https://go-review.googlesource.com/c/sys/+/613855.
Important tips:
- Don't comment on this PR. All discussion takes place in Gerrit.
- You need a Gmail or other Google account to log in to Gerrit.
- To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
- The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
- See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.
Message from Gopher Robot:
Patch Set 1:
(1 comment)
Please don’t reply on this GitHub thread. Visit golang.org/cl/613855. After addressing review feedback, remember to publish your drafts!
Message from Tobias Klauser:
Patch Set 1: Hold+1
(2 comments)
Please don’t reply on this GitHub thread. Visit golang.org/cl/613855. After addressing review feedback, remember to publish your drafts!
Message from Mauri de Souza Meneguzzo:
Patch Set 1:
(2 comments)
Please don’t reply on this GitHub thread. Visit golang.org/cl/613855. After addressing review feedback, remember to publish your drafts!
Message from Mauri de Souza Meneguzzo:
Patch Set 2:
(1 comment)
Please don’t reply on this GitHub thread. Visit golang.org/cl/613855. After addressing review feedback, remember to publish your drafts!
This PR (HEAD: e8502b93d8508e65243be6ed8d6ce912aecb1d23) has been imported to Gerrit for code review.
Please visit Gerrit at https://go-review.googlesource.com/c/sys/+/613855.
Important tips:
- Don't comment on this PR. All discussion takes place in Gerrit.
- You need a Gmail or other Google account to log in to Gerrit.
- To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
- The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
- See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.
Message from Mauri de Souza Meneguzzo:
Patch Set 2:
(1 comment)
Please don’t reply on this GitHub thread. Visit golang.org/cl/613855. After addressing review feedback, remember to publish your drafts!
Message from Mauri de Souza Meneguzzo:
Patch Set 3:
(1 comment)
Please don’t reply on this GitHub thread. Visit golang.org/cl/613855. After addressing review feedback, remember to publish your drafts!
Message from Mauri de Souza Meneguzzo:
Patch Set 3:
(1 comment)
Please don’t reply on this GitHub thread. Visit golang.org/cl/613855. After addressing review feedback, remember to publish your drafts!
Message from Ian Lance Taylor:
Patch Set 3:
(3 comments)
Please don’t reply on this GitHub thread. Visit golang.org/cl/613855. After addressing review feedback, remember to publish your drafts!
This PR (HEAD: ed9db1a77d00bd47cf5aa8500811673148868a36) has been imported to Gerrit for code review.
Please visit Gerrit at https://go-review.googlesource.com/c/sys/+/613855.
Important tips:
- Don't comment on this PR. All discussion takes place in Gerrit.
- You need a Gmail or other Google account to log in to Gerrit.
- To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
- The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
- See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.
Message from Mauri de Souza Meneguzzo:
Patch Set 4:
(2 comments)
Please don’t reply on this GitHub thread. Visit golang.org/cl/613855. After addressing review feedback, remember to publish your drafts!
Message from Ian Lance Taylor:
Patch Set 4: Commit-Queue+1
Please don’t reply on this GitHub thread. Visit golang.org/cl/613855. After addressing review feedback, remember to publish your drafts!
Message from Go LUCI:
Patch Set 4:
Dry run: CV is trying the patch.
Bot data: {"action":"start","triggered_at":"2024-09-27T05:09:06Z","revision":"a14947493e3577739033a2345fd8d05a0353b8fa"}
Please don’t reply on this GitHub thread. Visit golang.org/cl/613855. After addressing review feedback, remember to publish your drafts!
Message from Ian Lance Taylor:
Patch Set 4: -Commit-Queue
Please don’t reply on this GitHub thread. Visit golang.org/cl/613855. After addressing review feedback, remember to publish your drafts!
Message from Go LUCI:
Patch Set 4:
This CL has passed the run
Please don’t reply on this GitHub thread. Visit golang.org/cl/613855. After addressing review feedback, remember to publish your drafts!
Message from Go LUCI:
Patch Set 4: LUCI-TryBot-Result+1
Please don’t reply on this GitHub thread. Visit golang.org/cl/613855. After addressing review feedback, remember to publish your drafts!
Message from Tobias Klauser:
Patch Set 4: Code-Review+2 Hold+1
(2 comments)
Please don’t reply on this GitHub thread. Visit golang.org/cl/613855. After addressing review feedback, remember to publish your drafts!
This PR (HEAD: d09238ecd0989901b5d92e7a0ae2556c6e441d27) has been imported to Gerrit for code review.
Please visit Gerrit at https://go-review.googlesource.com/c/sys/+/613855.
Important tips:
- Don't comment on this PR. All discussion takes place in Gerrit.
- You need a Gmail or other Google account to log in to Gerrit.
- To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
- The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
- See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.
Message from Mauri de Souza Meneguzzo:
Patch Set 5:
(1 comment)
Please don’t reply on this GitHub thread. Visit golang.org/cl/613855. After addressing review feedback, remember to publish your drafts!
Message from Ian Lance Taylor:
Patch Set 5: Commit-Queue+1
Please don’t reply on this GitHub thread. Visit golang.org/cl/613855. After addressing review feedback, remember to publish your drafts!
Message from Go LUCI:
Patch Set 5:
Dry run: CV is trying the patch.
Bot data: {"action":"start","triggered_at":"2024-09-27T22:18:25Z","revision":"8a93e464c737328d7f1020dd7116053dc40c998d"}
Please don’t reply on this GitHub thread. Visit golang.org/cl/613855. After addressing review feedback, remember to publish your drafts!
Message from Ian Lance Taylor:
Patch Set 5: -Commit-Queue
Please don’t reply on this GitHub thread. Visit golang.org/cl/613855. After addressing review feedback, remember to publish your drafts!
Message from Go LUCI:
Patch Set 5:
This CL has passed the run
Please don’t reply on this GitHub thread. Visit golang.org/cl/613855. After addressing review feedback, remember to publish your drafts!
Message from Go LUCI:
Patch Set 5: LUCI-TryBot-Result+1
Please don’t reply on this GitHub thread. Visit golang.org/cl/613855. After addressing review feedback, remember to publish your drafts!
Message from Ian Lance Taylor:
Patch Set 5: Auto-Submit+1 Code-Review+2 Commit-Queue+1
(1 comment)
Please don’t reply on this GitHub thread. Visit golang.org/cl/613855. After addressing review feedback, remember to publish your drafts!
Message from Go LUCI:
Patch Set 5:
Dry run: CV is trying the patch.
Bot data: {"action":"start","triggered_at":"2024-09-27T22:47:14Z","revision":"8a93e464c737328d7f1020dd7116053dc40c998d"}
Please don’t reply on this GitHub thread. Visit golang.org/cl/613855. After addressing review feedback, remember to publish your drafts!
Message from Ian Lance Taylor:
Patch Set 5: -Commit-Queue
Please don’t reply on this GitHub thread. Visit golang.org/cl/613855. After addressing review feedback, remember to publish your drafts!
Message from Go LUCI:
Patch Set 5:
This CL has passed the run
Please don’t reply on this GitHub thread. Visit golang.org/cl/613855. After addressing review feedback, remember to publish your drafts!
This PR is being closed because golang.org/cl/613855 has been merged.