From: Kees Cook <kees@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Kees Cook <keescook@chromium.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>
Cc: 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 kspp tree
Date: Tue, 27 Feb 2024 19:26:26 -0800 [thread overview]
Message-ID: <31C7C387-221F-4FEA-887E-A262844EE9CB@kernel.org> (raw)
In-Reply-To: <20240228140252.6d4e5e85@canb.auug.org.au>
On February 27, 2024 7:02:52 PM PST, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>Hi all,
>
>The following commit is also in the tip tree as a different commit
>(but the same patch):
>
> 2867ef32ce00 ("x86/vdso: Move vDSO to mmap region")
>
>This is commit
>
> 3c6539b4c177 ("x86/vdso: Move vDSO to mmap region")
>
>in the tip tree.
Thanks! I'll drop mine.
-Kees
--
Kees Cook
next prev parent reply other threads:[~2024-02-28 3:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 3:02 linux-next: duplicate patch in the kspp tree Stephen Rothwell
2024-02-28 3:26 ` Kees Cook [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-26 7:52 Stephen Rothwell
2025-05-09 8:48 Stephen Rothwell
2025-05-09 16:32 ` Kees Cook
2025-05-13 1:32 ` Martin K. Petersen
2025-04-22 9:44 Stephen Rothwell
2025-04-22 15:51 ` Kees Cook
2024-11-04 5:42 Stephen Rothwell
2024-11-04 6:41 ` Andrew Morton
2024-07-08 8:24 Stephen Rothwell
2024-07-08 19:20 ` Kees Cook
2024-01-04 3:23 Stephen Rothwell
2024-01-04 3:26 ` Stephen Rothwell
2023-06-05 2:34 Stephen Rothwell
2023-06-01 2:30 Stephen Rothwell
2023-06-01 2:43 ` Kees Cook
2023-06-01 4:12 ` Andrew Morton
2023-01-17 4:02 Stephen Rothwell
2023-01-17 13:52 ` Karol Herbst
2023-01-17 20:56 ` Stephen Rothwell
2023-01-18 20:38 ` Kees Cook
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=31C7C387-221F-4FEA-887E-A262844EE9CB@kernel.org \
--to=kees@kernel.org \
--cc=hpa@zytor.com \
--cc=keescook@chromium.org \
--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