From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Shuah Khan <shuah@kernel•org>,
Thomas Gleixner <tglx@linutronix•de>,
Ingo Molnar <mingo@redhat•com>, "H. Peter Anvin" <hpa@zytor•com>,
Peter Zijlstra <peterz@infradead•org>
Cc: Binbin Wu <binbin.wu@linux•intel.com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: duplicate patch in the kselftest tree
Date: Tue, 17 Oct 2023 15:03:25 +1100 [thread overview]
Message-ID: <20231017150325.4a89ab71@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 318 bytes --]
Hi all,
The following commit is also in the tip tree as a different commit
(but the same patch):
197964fc3274 ("selftests/x86/lam: Zero out buffer for readlink()")
This is commit
29060633411a ("selftests/x86/lam: Zero out buffer for readlink()")
in the tip tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-10-17 4:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 4:03 Stephen Rothwell [this message]
2023-10-17 15:18 ` linux-next: duplicate patch in the kselftest tree Shuah Khan
2023-10-18 10:44 ` Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2025-11-20 5:23 Stephen Rothwell
2025-11-20 5:42 ` Masami Hiramatsu
2025-07-02 6:36 Stephen Rothwell
2025-07-02 15:57 ` Shuah Khan
2025-07-02 18:06 ` Andrew Morton
2024-04-15 4:43 Stephen Rothwell
2024-04-16 23:54 ` Shuah Khan
2023-06-05 23:02 Stephen Rothwell
2023-06-05 23:21 ` Shuah Khan
2023-03-29 1:23 Stephen Rothwell
2023-04-23 16:06 ` Shuah Khan
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=20231017150325.4a89ab71@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=binbin.wu@linux$(echo .)intel.com \
--cc=hpa@zytor$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mingo@redhat$(echo .)com \
--cc=peterz@infradead$(echo .)org \
--cc=shuah@kernel$(echo .)org \
--cc=tglx@linutronix$(echo .)de \
/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