From: Herbert Xu <herbert@gondor.apana.org.au>
To: "Cabiddu, Giovanni" <giovanni.cabiddu@intel.com>
Cc: Alex Williamson <alex.williamson@redhat.com>,
"Zeng, Xin" <xin.zeng@intel.com>,
"Tian, Kevin" <kevin.tian@intel.com>,
Arnd Bergmann <arnd@arndb.de>, Jason Gunthorpe <jgg@ziepe.ca>,
Yishai Hadas <yishaih@nvidia.com>,
Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>,
"Cao, Yahui" <yahui.cao@intel.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
qat-linux <qat-linux@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] vfio/qat: add PCI_IOV dependency
Date: Tue, 11 Jun 2024 11:20:50 +0800 [thread overview]
Message-ID: <ZmfCkiuiag34_mjO@gondor.apana.org.au> (raw)
In-Reply-To: <ZmcbNa4yn+/0NnTD@gcabiddu-mobl.ger.corp.intel.com>
On Mon, Jun 10, 2024 at 04:26:59PM +0100, Cabiddu, Giovanni wrote:
> On Fri, Jun 07, 2024 at 03:34:06PM -0600, Alex Williamson wrote:
> > Is this then being taken care of in the QAT PF driver? Are there
> > patches posted targeting v6.10?
> Yes. This is being taken care in the QAT PF driver. Xin just sent a fix
> for it [1].
> @Herbert, can this be sent to stable after the review?
This patch wasn't sent to linux-crypto so I cannot apply it.
In any case, is there any reason why the fix can't go through the
vfio tree?
Cheers,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2024-06-11 3:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 12:04 Arnd Bergmann
2024-05-29 2:25 ` Tian, Kevin
2024-05-29 3:11 ` Zeng, Xin
2024-05-29 5:35 ` Tian, Kevin
2024-05-31 2:56 ` Zeng, Xin
2024-06-07 21:34 ` Alex Williamson
2024-06-10 15:26 ` Cabiddu, Giovanni
2024-06-11 3:20 ` Herbert Xu [this message]
2024-06-11 11:27 ` Cabiddu, Giovanni
2024-06-11 15:22 ` Herbert Xu
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=ZmfCkiuiag34_mjO@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=alex.williamson@redhat.com \
--cc=arnd@arndb.de \
--cc=giovanni.cabiddu@intel.com \
--cc=jgg@ziepe.ca \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qat-linux@intel.com \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=xin.zeng@intel.com \
--cc=yahui.cao@intel.com \
--cc=yishaih@nvidia.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
all inboxes | Powered by JetHome®