From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Dan Williams <dan.j.williams@intel•com>
Cc: 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 nvdimm tree
Date: Wed, 3 Jan 2024 15:23:45 +1100 [thread overview]
Message-ID: <20240103152345.116ce8c7@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 348 bytes --]
Hi all,
The following commit is also in the char-misc tree as a different commit
(but the same patch):
ce2fa3e597dd ("tools/testing/nvdimm: Add compile-test coverage for ndtest")
This is commit
fddd9e3e4e71 ("tools/testing/nvdimm: Add compile-test coverage for ndtest")
in the char-misc tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2024-01-03 4:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-03 4:23 Stephen Rothwell [this message]
2024-01-03 19:30 ` linux-next: duplicate patch in the nvdimm tree Dan Williams
2024-01-03 20:32 ` Ira Weiny
-- strict thread matches above, loose matches on Subject: below --
2023-09-27 2:32 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=20240103152345.116ce8c7@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=dan.j.williams@intel$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.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