From: Andrew Morton <akpm@linux-foundation•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Christian Brauner <brauner@kernel•org>,
Christophe JAILLET <christophe.jaillet@wanadoo•fr>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: duplicate patch in the vfs-brauner tree
Date: Wed, 12 Jun 2024 19:21:41 -0700 [thread overview]
Message-ID: <20240612192141.69896438b5f6e674e07d418e@linux-foundation.org> (raw)
In-Reply-To: <20240613104837.346519cc@canb.auug.org.au>
On Thu, 13 Jun 2024 10:48:37 +1000 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
> Hi all,
>
> The following commits are also in Linus Torvalds' tree as different
> commits (but the same patch):
>
> 08ce6f724ce9 ("proc: Remove usage of the deprecated ida_simple_xx() API")
>
> This is commit
>
> d92c9986e4db ("proc: remove usage of the deprecated ida_simple_xx() API")
>
> in the mm-nonmm-unstable branch of the mm tree.
That's one patch from a three-patch series in a different tree.
Also,
hp2:/usr/src/mm> git log fs/proc/ | grep "Signed-off-by.*brauner" | wc -l
22
hp2:/usr/src/mm> git log fs/proc/ | grep "Signed-off-by.*akpm" | wc -l
1211
Christian, if procfs patches are to henceforth go via the vfs tree,
let's be a bit more organized about it?
next prev parent reply other threads:[~2024-06-13 2:21 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 0:48 linux-next: duplicate patch in the vfs-brauner tree Stephen Rothwell
2024-06-13 0:51 ` Stephen Rothwell
2024-06-13 2:21 ` Andrew Morton [this message]
2024-06-13 12:17 ` Christian Brauner
2024-06-13 19:43 ` Andrew Morton
2024-06-13 20:06 ` Marion & Christophe JAILLET
-- strict thread matches above, loose matches on Subject: below --
2025-12-18 5:32 Stephen Rothwell
2025-08-21 1:02 Stephen Rothwell
2025-08-21 5:24 ` Greg KH
2025-07-07 23:51 Stephen Rothwell
2025-07-08 8:35 ` Christian Brauner
2025-07-08 21:51 ` Stephen Rothwell
2025-05-20 23:45 Stephen Rothwell
2025-05-20 23:48 ` Stephen Rothwell
2025-04-16 22:49 Stephen Rothwell
2025-04-22 8:03 ` Christian Brauner
2025-01-16 1:16 Stephen Rothwell
2025-01-19 21:06 ` Stephen Rothwell
2025-01-09 0:18 Stephen Rothwell
2025-01-20 21:39 ` Stephen Rothwell
2024-08-25 22:24 Stephen Rothwell
2024-08-26 12:13 ` Christian Brauner
2024-08-15 22:55 Stephen Rothwell
2024-07-01 3:21 Stephen Rothwell
2024-03-18 21:23 Stephen Rothwell
2024-03-06 22:02 Stephen Rothwell
2024-02-05 5:23 Stephen Rothwell
2023-09-14 23:39 Stephen Rothwell
2023-09-18 20:52 ` Darrick J. Wong
2023-09-19 12:34 ` Christian Brauner
2023-09-19 15:43 ` Darrick J. Wong
2023-09-20 12:09 ` Christian Brauner
2023-08-06 22:37 Stephen Rothwell
2023-07-17 0:11 Stephen Rothwell
2023-07-19 6:16 ` Christian Brauner
2023-07-19 23:28 ` Tyler Hicks
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240612192141.69896438b5f6e674e07d418e@linux-foundation.org \
--to=akpm@linux-foundation$(echo .)org \
--cc=brauner@kernel$(echo .)org \
--cc=christophe.jaillet@wanadoo$(echo .)fr \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox