public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nicolin Chen <nicolinc@nvidia.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: <will@kernel.org>, <robin.murphy@arm.com>, <jgg@nvidia.com>,
	<kevin.tian@intel.com>, <quic_jjohnson@quicinc.com>,
	<suravee.suthikulpanit@amd.com>, <robdclark@gmail.com>,
	<dwmw2@infradead.org>, <baolu.lu@linux.intel.com>,
	<yong.wu@mediatek.com>, <matthias.bgg@gmail.com>,
	<orsonzhai@gmail.com>, <baolin.wang@linux.alibaba.com>,
	<zhang.lyra@gmail.com>, <thierry.reding@gmail.com>,
	<vdumpa@nvidia.com>, <jonathanh@nvidia.com>,
	<jean-philippe@linaro.org>,
	<shameerali.kolothum.thodi@huawei.com>, <tglx@linutronix.de>,
	<christophe.jaillet@wanadoo.fr>, <thunder.leizhen@huawei.com>,
	<yangyingliang@huawei.com>, <quic_saipraka@quicinc.com>,
	<jon@solid-run.com>, <iommu@lists.linux.dev>,
	<linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-arm-msm@vger.kernel.org>,
	<linux-mediatek@lists.infradead.org>,
	<linux-tegra@vger.kernel.org>,
	<virtualization@lists.linux-foundation.org>
Subject: Re: [PATCH v6 0/5] Define EINVAL as device/domain incompatibility
Date: Mon, 26 Sep 2022 15:34:19 -0700	[thread overview]
Message-ID: <YzIo67x8Ap6Eiruz@Asurada-Nvidia> (raw)
In-Reply-To: <YzGZqXCuw6yoXBla@8bytes.org>

On Mon, Sep 26, 2022 at 02:23:05PM +0200, Joerg Roedel wrote:
> External email: Use caution opening links or attachments
> 
> 
> Hi Nicolin,
> 
> On Fri, Sep 23, 2022 at 12:16:29AM -0700, Nicolin Chen wrote:
> > This series is to replace the previous EMEDIUMTYPE patch in a VFIO series:
> > https://lore.kernel.org/kvm/Yxnt9uQTmbqul5lf@8bytes.org/
> 
> \o/
> 
> > Nicolin Chen (5):
> >   iommu/amd: Drop unnecessary checks in amd_iommu_attach_device()
> >   iommu: Add return value rules to attach_dev op and APIs
> >   iommu: Regulate EINVAL in ->attach_dev callback functions
> >   iommu: Use EINVAL for incompatible device/domain in ->attach_dev
> >   iommu: Propagate return value in ->attach_dev callback functions
> 
> This looks good to me, but I'd like to have the SMMU people have a look
> at patch 4. And I think it is too late for this to make it into 6.1, so
> please re-send after 6.1-rc1 is out.

Robin has given review comments against the similar patch in the
EMEDIUMTYPE series, though it'd be nicer to have a Reviewed-by.

I will re-send them rebasing on v6.1rc1.

Thanks!
Nic

      reply	other threads:[~2022-09-26 22:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-23  7:16 [PATCH v6 0/5] Define EINVAL as device/domain incompatibility Nicolin Chen
2022-09-23  7:17 ` [PATCH v6 1/5] iommu/amd: Drop unnecessary checks in amd_iommu_attach_device() Nicolin Chen
2022-09-23  7:17 ` [PATCH v6 2/5] iommu: Add return value rules to attach_dev op and APIs Nicolin Chen
2022-09-23  7:17 ` [PATCH v6 3/5] iommu: Regulate EINVAL in ->attach_dev callback functions Nicolin Chen
2022-09-23  7:18 ` [PATCH v6 4/5] iommu: Use EINVAL for incompatible device/domain in ->attach_dev Nicolin Chen
2022-09-23  7:18 ` [PATCH v6 5/5] iommu: Propagate return value in ->attach_dev callback functions Nicolin Chen
2022-09-26 12:23 ` [PATCH v6 0/5] Define EINVAL as device/domain incompatibility Joerg Roedel
2022-09-26 22:34   ` Nicolin Chen [this message]

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=YzIo67x8Ap6Eiruz@Asurada-Nvidia \
    --to=nicolinc@nvidia.com \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=baolu.lu@linux.intel.com \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=dwmw2@infradead.org \
    --cc=iommu@lists.linux.dev \
    --cc=jean-philippe@linaro.org \
    --cc=jgg@nvidia.com \
    --cc=jon@solid-run.com \
    --cc=jonathanh@nvidia.com \
    --cc=joro@8bytes.org \
    --cc=kevin.tian@intel.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=matthias.bgg@gmail.com \
    --cc=orsonzhai@gmail.com \
    --cc=quic_jjohnson@quicinc.com \
    --cc=quic_saipraka@quicinc.com \
    --cc=robdclark@gmail.com \
    --cc=robin.murphy@arm.com \
    --cc=shameerali.kolothum.thodi@huawei.com \
    --cc=suravee.suthikulpanit@amd.com \
    --cc=tglx@linutronix.de \
    --cc=thierry.reding@gmail.com \
    --cc=thunder.leizhen@huawei.com \
    --cc=vdumpa@nvidia.com \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=will@kernel.org \
    --cc=yangyingliang@huawei.com \
    --cc=yong.wu@mediatek.com \
    --cc=zhang.lyra@gmail.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