From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Eric Biggers <ebiggers@kernel.org>,
Kent Overstreet <kent.overstreet@linux.dev>
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 crc tree
Date: Mon, 9 Dec 2024 14:57:14 +1100 [thread overview]
Message-ID: <20241209145714.1619f9d2@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 332 bytes --]
Hi all,
The following commit is also in the bcachefs tree as a different commit
(but the same patch):
cc354fa7f016 ("bcachefs: Explicitly select CRYPTO from BCACHEFS_FS")
This is commit
4fa882d383cc ("bcachefs: Explicitly select CRYPTO from BCACHEFS_FS")
in the bcachefs tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2024-12-09 3:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 3:57 Stephen Rothwell [this message]
2024-12-09 4:30 ` linux-next: duplicate patch in the crc tree Eric Biggers
2024-12-09 4:55 ` Kent Overstreet
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=20241209145714.1619f9d2@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=ebiggers@kernel.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/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