From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>,
Joey Gouly <joey.gouly@arm.com>, Peter Xu <peterx@redhat.com>,
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 mm-hotfixes tree
Date: Wed, 15 Mar 2023 13:13:00 +1100 [thread overview]
Message-ID: <20230315131300.7776ce0e@canb.auug.org.au> (raw)
In-Reply-To: <20230314082447.46640d77@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 567 bytes --]
Hi all,
On Tue, 14 Mar 2023 08:24:47 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> The following commit is also in Linus Torvalds' tree as a different commit
> (but the same patch):
>
> a1713ab0740f ("tools headers UAPI: Sync linux/prctl.h with the kernel sources")
The above is now commit
36714de4fa54 ("tools headers UAPI: sync linux/prctl.h with the kernel sources")
> This is commit
>
> df4b933e0e51 ("tools headers UAPI: Sync linux/prctl.h with the kernel sources")
>
> in Linus' tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-03-15 2:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 21:24 linux-next: duplicate patch in the mm-hotfixes tree Stephen Rothwell
2023-03-15 2:13 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-21 22:10 Stephen Rothwell
2023-10-02 20:47 Stephen Rothwell
2023-06-07 22:47 Stephen Rothwell
2023-02-27 1:28 Stephen Rothwell
2023-02-12 21:00 Stephen Rothwell
2023-02-13 21:54 ` Stephen Rothwell
2023-02-13 22:29 ` Andrew Morton
2023-02-14 0:09 ` Stephen Rothwell
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=20230315131300.7776ce0e@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=acme@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=joey.gouly@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=peterx@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).