From: Christian Brauner <brauner@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patches in the vfs-brauner tree
Date: Fri, 10 Jan 2025 12:08:04 +0100 [thread overview]
Message-ID: <20250110-siedler-karnickel-d6a5e3904c9c@brauner> (raw)
In-Reply-To: <20250106191417.0f7707a0ecbf1a386ef60538@linux-foundation.org>
On Mon, Jan 06, 2025 at 07:14:17PM -0800, Andrew Morton wrote:
> On Mon, 6 Jan 2025 10:10:38 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> > Hi all,
> >
> > The following commits are also in the mm-hotfixes and mm trees as
> > different commits (but the same patches):
> >
> > 15858da53542 ("selftests: coredump: Add stackdump test")
> > ab251dacfbae ("fs/proc: do_task_stat: Fix ESP not readable during coredump")
> >
> > These are commits
> >
> > 1e0ad4a1359b ("selftests: coredump: add stackdump test")
> >
> > from the mm-nonmm-unstable branch of the mm tree, and
> >
> > 7cc55ae2737b ("fs/proc: do_task_stat: fix ESP not readable during coredump")
> >
> > from the mm-hotfixes-unstable branch of the mm-hotfixes tree.
>
> I'll drop the mm.git copies.
>
> Christian,
>
> hp2:/usr/src/mm> git log fs/proc | grep "Signed.*akpm" | wc -l
> 1231
>
> if you wish to change this then please discuss with me.
Ah sorry, I just saw this message now.
Sorry, since fs/proc/ is just listed as fsdevel I picked them up.
I'm happy to take them going forward unless it has obvious interactions
with mm.
Let me know what you think.
next prev parent reply other threads:[~2025-01-10 11:08 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-05 23:10 Stephen Rothwell
2025-01-07 3:14 ` Andrew Morton
2025-01-10 11:08 ` Christian Brauner [this message]
2025-01-11 0:31 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2025-10-19 20:29 Stephen Rothwell
2025-01-20 22:20 Stephen Rothwell
2025-01-12 21:55 Stephen Rothwell
2024-10-20 11:08 Stephen Rothwell
2024-10-21 8:22 ` Christian Brauner
2024-10-15 22:02 Stephen Rothwell
2024-07-31 23:54 Stephen Rothwell
2024-07-24 22:00 Stephen Rothwell
2024-04-03 23:10 Stephen Rothwell
2024-04-03 23:59 ` Dominique Martinet
2024-04-04 0:21 ` Randy Dunlap
2024-04-04 1:44 ` Dominique Martinet
2024-04-05 10:57 ` Christian Brauner
2024-04-05 11:30 ` Dominique Martinet
2024-04-05 13:09 ` Christian Brauner
2024-04-04 2:09 ` Andrew Morton
2023-12-21 0:00 Stephen Rothwell
2023-12-21 10:50 ` David Howells
2023-10-18 23:12 Stephen Rothwell
2023-10-19 5:36 ` Amir Goldstein
2023-10-19 9:18 ` Christian Brauner
2023-10-12 23:48 Stephen Rothwell
2023-10-13 6:32 ` Amir Goldstein
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=20250110-siedler-karnickel-d6a5e3904c9c@brauner \
--to=brauner@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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
all inboxes | Powered by JetHome®