Message ID | 20240724210014.mc6nima6cekgiukx@joelS2.panther.com (mailing list archive) |
---|---|
State | Not Applicable |
Headers | show |
Series | [GIT,PULL] sysctl constification changes for v6.11-rc1 | expand |
Context | Check | Description |
---|---|---|
netdev/tree_selection | success | Pull request for net |
netdev/build_32bit | success | Errors and warnings before: 992 this patch: 737 |
netdev/build_tools | success | Errors and warnings before: 10 this patch: 10 |
netdev/build_clang | success | Errors and warnings before: 1494 this patch: 1234 |
netdev/verify_signedoff | success | Signed-off-by tag matches author and committer |
netdev/verify_fixes | fail | Problems with Fixes tag: 18 |
netdev/build_allmodconfig_warn | success | Errors and warnings before: 16049 this patch: 15803 |
netdev/build_clang_rust | success | No Rust files in patch. Skipping build |
netdev/kdoc | success | Errors and warnings before: 0 this patch: 0 |
netdev/contest | fail | net-next-2024-07-25--03-00 (tests: 679) |
On Wed, 24 Jul 2024 at 14:00, Joel Granados <j.granados@samsung.com> wrote: > > This is my first time sending out a semantic patch, so get back to me if > you have issues or prefer some other way of receiving it. Looks fine to me. Sometimes if it's just a pure scripting change, people send me the script itself and just ask me to run it as a final thing before the rc1 release or something like that. But since in practice there's almost always some additional manual cleanup, doing it this way with the script documented in the commit is typically the right way to go. This time it was details like whitespace alignment, sometimes it's "the script did 95%, but there was another call site that also needed updating", or just a documentation update to go in together with the change or whatever. Anyway, pulled and just going through my build tests now. Linus
The pull request you sent on Wed, 24 Jul 2024 23:00:14 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/sysctl/sysctl.git/ tags/constfy-sysctl-6.11-rc1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/b485625078cab3b824a84ce185b6e73733704b5b
Thank you!
Hello: This pull request was applied to riscv/linux.git (fixes) by Linus Torvalds <torvalds@linux-foundation.org>: On Wed, 24 Jul 2024 23:00:14 +0200 you wrote: > Linus > > Constifying ctl_table structs will prevent the modification of > proc_handler function pointers as they would reside in .rodata. To get > there, the proc_handler arguments must first be const qualified which > requires this (fairly large) treewide PR. Sending it in the tail end of > of the merge window after a suggestion from Kees to avoid unneeded merge > conflicts. It has been rebased on top of 7a3fad30fd8b4b5e370906b3c554f64026f56c2f. > I can send it later if it makes more sense on your side; please tell me > what you prefer. > > [...] Here is the summary with links: - [GIT,PULL] sysctl constification changes for v6.11-rc1 https://git.kernel.org/riscv/c/f8a8b94d0698 You are awesome, thank you!
Hello: This pull request was applied to riscv/linux.git (for-next) by Linus Torvalds <torvalds@linux-foundation.org>: On Wed, 24 Jul 2024 23:00:14 +0200 you wrote: > Linus > > Constifying ctl_table structs will prevent the modification of > proc_handler function pointers as they would reside in .rodata. To get > there, the proc_handler arguments must first be const qualified which > requires this (fairly large) treewide PR. Sending it in the tail end of > of the merge window after a suggestion from Kees to avoid unneeded merge > conflicts. It has been rebased on top of 7a3fad30fd8b4b5e370906b3c554f64026f56c2f. > I can send it later if it makes more sense on your side; please tell me > what you prefer. > > [...] Here is the summary with links: - [GIT,PULL] sysctl constification changes for v6.11-rc1 https://git.kernel.org/riscv/c/b485625078ca You are awesome, thank you!