From: Yoan Picchi <yoan.picchi@foss.arm.com>
To: yoan.picchi@arm.com, andre.przywara@arm.com, ardb@kernel.org,
davem@davemloft.net, giovanni.cabiddu@intel.com,
herbert@gondor.apana.org.au, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org, qat-linux@intel.com
Subject: Re: [PATCH 0/2] Crypto: Remove x86 dependency on QAT drivers
Date: Fri, 17 Jun 2022 11:10:34 +0100 [thread overview]
Message-ID: <a048a5ae-5f1e-d2ea-8152-09de4b6e420e@foss.arm.com> (raw)
In-Reply-To: <20220617095548.436758-1-yoan.picchi@arm.com>
Please disregard this post, I sent the wrong patch by mistake. Please
look at the [PATCH v3 0/2] instead.
next prev parent reply other threads:[~2022-06-17 10:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 9:55 [PATCH 0/2] Crypto: Remove x86 dependency on QAT drivers Yoan Picchi
2022-06-17 10:10 ` Yoan Picchi [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-06-13 14:25 Yoan Picchi
2022-06-17 8:49 ` Giovanni Cabiddu
2022-06-07 16:58 Yoan Picchi
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=a048a5ae-5f1e-d2ea-8152-09de4b6e420e@foss.arm.com \
--to=yoan.picchi@foss.arm.com \
--cc=andre.przywara@arm.com \
--cc=ardb@kernel.org \
--cc=davem@davemloft.net \
--cc=giovanni.cabiddu@intel.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qat-linux@intel.com \
--cc=yoan.picchi@arm.com \
/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