From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Shuah Khan <shuah@kernel•org>, Andrew Morton <akpm@linux-foundation•org>
Cc: Ivan Orlov <ivan.orlov0322@gmail•com>,
Shuah Khan <skhan@linuxfoundation•org>,
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: Wed, 29 Mar 2023 12:23:19 +1100 [thread overview]
Message-ID: <20230329122319.76b73d11@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 350 bytes --]
Hi all,
The following commit is also in the mm tree as a different commit (but
the same patch):
c83f320e55a4 ("selftests: cgroup: Add 'malloc' failures checks in test_memcontrol")
This is commit
afea51f8cf60 ("selftests: cgroup: add 'malloc' failures checks in test_memcontrol")
in the mm tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-03-29 1:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 1:23 Stephen Rothwell [this message]
2023-04-23 16:06 ` linux-next: duplicate patch in the kselftest tree Shuah Khan
-- strict thread matches above, loose matches on Subject: below --
2023-06-05 23:02 Stephen Rothwell
2023-06-05 23:21 ` Shuah Khan
2023-10-17 4:03 Stephen Rothwell
2023-10-17 15:18 ` Shuah Khan
2023-10-18 10:44 ` Ingo Molnar
2024-04-15 4:43 Stephen Rothwell
2024-04-16 23:54 ` Shuah Khan
2025-07-02 6:36 Stephen Rothwell
2025-07-02 15:57 ` Shuah Khan
2025-07-02 18:06 ` Andrew Morton
2025-11-20 5:23 Stephen Rothwell
2025-11-20 5:42 ` Masami Hiramatsu
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=20230329122319.76b73d11@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=akpm@linux-foundation$(echo .)org \
--cc=ivan.orlov0322@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=shuah@kernel$(echo .)org \
--cc=skhan@linuxfoundation$(echo .)org \
/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