lkml.org 
[lkml]   [2024]   [Apr]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH v2 00/11] sysctl: treewide: constify ctl_table argument of sysctl handlers
On Tue, Apr 16, 2024 at 09:32:24PM +0200, Thomas Weißschuh wrote:
> (+Cc LKML to at least get the conversation into the archives)
>
> Hi Joel,
...
>
> > Not only that, but it also breaks tools like lei and b4. I have configured b4 to
> > look at https://lore.kernel.org/all to handle patches coming from contributors.
> > If the change is not public it breaks my command (`b4 am -o - MESSAGE_ID | git
> > am -3`).
>
> Understood, as mentioned above the trimming went to far.
>
> FYI:
> b4 can do the `git am` itself with `b4 shazam MESSAGE_ID`.
> Use the config `b4.shazam-am-flags` for the `-3` flag.

Thx for the tip.

>
> > I do not know who spooked you but I suggest you just remove this person
> > from the to:/cc: of your patches and leave the rest as it is. Like I
> > did with Mathew Wilcox after he asked me to do so here
> > https://lore.kernel.org/all/ZZbJRiN8ENV%2FFoTV@casper.infradead.org/.
> > Please resend the patchset including the relevant kernel mailing lists and
> > maintainers but excepting the person that sent you the private e-mail.
>
> In addition to the complaint I also got guidance from Thomas Gleixner to
> reduce the scope of recipients.
>
> What do you think about the following:
>
> You do a review of v2 and give feedback on that and I'll incorporate
> that feedback and afterwards send a v3.
This will *not* work and this is why:
1. I will not be able to use b4 to gather SOBs (and the like) because
there is no original mail
2. The review would be confusing in public as the original message will
not have existed.
3. I will most likely forget to add relevant recepients.

Please resend the patch. `b4 send --resend [vN]` should work after you
have added the additional CCs.

> In addition to the recipients of v2 I'll add LKML, Greg and Andrew Morton.
It will just get lost in LKML. If you are *not* going to add all the
maintainers themselves, at least add the relevant kernel lists. These
are the lists that I propose (from running get_maintainers.pl on your
11/11 patch):

linux-fsdevel@vger.kernel.org
netdev@vger.kernel.org
linux-arm-kernel@lists.infradead.org
linux-s390@vger.kernel.org
linux-kernel@vger.kernel.org
linux-riscv@lists.infradead.org
linux-mm@kvack.org
linux-security-module@vger.kernel.org
bpf@vger.kernel.org
linuxppc-dev@lists.ozlabs.org
linux-xfs@vger.kernel.org
linux-trace-kernel@vger.kernel.org
linux-perf-users@vger.kernel.org
netfilter-devel@vger.kernel.org
coreteam@netfilter.org
kexec@lists.infradead.org
linux-hardening@vger.kernel.org
bridge@lists.linux.dev
lvs-devel@vger.kernel.org
linux-rdma@vger.kernel.org
rds-devel@oss.oracle.com
linux-sctp@vger.kernel.org
linux-nfs@vger.kernel.org
apparmor@lists.ubuntu.com

Its a long list because that patch touches everything :)


>
> > This also goes for your "[PATCH] sysctl: treewide: constify ctl_table_header::ctl_table_arg"
> > which is also not public.
>
> Thanks for this pointer, too.
> I'd like to handle it the same way as proposed above.
>
>
> Sorry for all the back-and-forth,
> Thomas

Best

--

Joel Granados
[unhandled content-type:application/pgp-signature]
\
 
 \ /
  Last update: 2024-04-17 09:37    [W:0.051 / U:1.032 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site