linux-kernel - Re: linux-next: duplicate patch in the vfs-brauner tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <35b8a2e6-dc26-456e-be93-e929c6c8ca64@wanadoo.fr>
Date: Thu, 13 Jun 2024 22:06:50 +0200
From: Marion & Christophe JAILLET <christophe.jaillet@...adoo.fr>
To: Andrew Morton <akpm@...ux-foundation.org>,
 Christian Brauner <brauner@...nel.org>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
 Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
 Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: duplicate patch in the vfs-brauner tree


Le 13/06/2024 à 21:43, Andrew Morton a écrit :
> On Thu, 13 Jun 2024 14:17:01 +0200 Christian Brauner <brauner@...nel.org> wrote:
>
>>> Christian, if procfs patches are to henceforth go via the vfs tree,
>>> let's be a bit more organized about it?
>> Sure. I simply didn't see any any "applied" message from you so I just
>> assumed to pick the parts that are relevant. Sorry about that.
> No probs.  If the author didn't cc you then my remember-to-cc-christian
> brain cell is unreliable :(

I guess, that the author is me.

in my .gitconfig, I use

[sendemail.linux]
     tocmd ="`pwd`/scripts/get_maintainer.pl --nogit --nogit-fallback 
--norolestats --nol"
     cccmd ="`pwd`/scripts/get_maintainer.pl --nogit --nogit-fallback 
--norolestats --nom"

and

 >scripts/get_maintainer.pl --nogit --nogit-fallback --norolestats --nol 
fs/proc/generic.c
[EMPTY OUTPUT]

 >scripts/get_maintainer.pl --nogit --nogit-fallback --norolestats --nol 
fs/proc/generic.c
linux-kernel@...r.kernel.org
linux-fsdevel@...r.kernel.org


Should MAINTAINERS be updated somewhere?


(sorry for the mess I've generated :( )


CJ


>
> It'll be at https://lore.kernel.org/mm-commits/ but that's a hassle.
>