From: Stephen Rothwell <sfr@canb•auug.org.au>
To: "Michael S. Tsirkin" <mst@redhat•com>,
Herbert Xu <herbert@gondor•apana.org.au>
Cc: Linux Crypto List <linux-crypto@vger•kernel.org>,
Li RongQing <lirongqing@baidu•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 vhost tree
Date: Fri, 23 Feb 2024 14:25:46 +1100 [thread overview]
Message-ID: <20240223142546.073f7c21@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 340 bytes --]
Hi all,
The following commit is also in the crypto tree as a different commit
(but the same patch):
2374ca8f6556 ("virtio_crypto: remove duplicate check if queue is broken")
This is commit
633eeefab69e ("crypto: virtio - remove duplicate check if queue is broken")
in the crypto tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2024-02-23 3:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 3:25 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-08-27 2:46 linux-next: duplicate patch in the vhost tree Stephen Rothwell
2025-08-27 10:23 ` Michael S. Tsirkin
2025-08-27 17:26 ` Namhyung Kim
2025-08-27 22:04 ` Michael S. Tsirkin
2025-08-27 23:50 ` Namhyung Kim
2024-10-24 4:15 Stephen Rothwell
2024-09-11 7:47 Stephen Rothwell
2024-09-11 10:41 ` Michael S. Tsirkin
2024-07-18 5:01 Stephen Rothwell
2024-07-18 5:16 ` Greg KH
2024-05-14 6:18 Stephen Rothwell
2024-01-05 4:06 Stephen Rothwell
2023-06-05 2:24 Stephen Rothwell
2023-04-11 5:19 Stephen Rothwell
2023-04-11 22:18 ` Jonathan Corbet
2023-04-12 2:51 ` Michael S. Tsirkin
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=20240223142546.073f7c21@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=herbert@gondor$(echo .)apana.org.au \
--cc=linux-crypto@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=lirongqing@baidu$(echo .)com \
--cc=mst@redhat$(echo .)com \
/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