From: Andrew Morton <akpm@linux-foundation.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>,
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 tip tree
Date: Fri, 2 Jun 2023 10:05:00 -0700 [thread overview]
Message-ID: <20230602100500.2416fabea876b03b129bbf23@linux-foundation.org> (raw)
In-Reply-To: <20230602130423.424e37cd@canb.auug.org.au>
On Fri, 2 Jun 2023 13:04:23 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi all,
>
> The following commit is also in the mm tree as a different commit (but
> the same patch):
>
> b7a7ce1bb77b ("vdso/timens: Always provide arch_get_vdso_data() prototype for vdso")
>
> This is commit
>
> 0361c2513d36 ("time_namespace: always provide arch_get_vdso_data() prototype for vdso")
>
> in the mm tree.
Thanks. I think I'll leave things as-is - both trees want the patch.
next prev parent reply other threads:[~2023-06-02 17:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 3:04 linux-next: duplicate patch in the tip tree Stephen Rothwell
2023-06-02 17:05 ` Andrew Morton [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-11 21:28 Stephen Rothwell
2023-10-04 2:33 Stephen Rothwell
2023-10-04 13:32 ` Jonathan Corbet
2023-10-04 15:41 ` Ingo Molnar
2023-01-13 1:40 Stephen Rothwell
2023-01-13 16:27 ` Jonathan Corbet
2023-01-13 21:51 ` 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=20230602100500.2416fabea876b03b129bbf23@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
/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).