From: Nicolin Chen <nicolinc@nvidia.com>
To: <joro@8bytes.org>, <suravee.suthikulpanit@amd.com>,
<will@kernel.org>, <robin.murphy@arm.com>, <robdclark@gmail.com>,
<dwmw2@infradead.org>, <baolu.lu@linux.intel.com>,
<agross@kernel.org>, <bjorn.andersson@linaro.org>,
<konrad.dybcio@somainline.org>, <matthias.bgg@gmail.com>,
<heiko@sntech.de>, <orsonzhai@gmail.com>,
<baolin.wang@linux.alibaba.com>, <zhang.lyra@gmail.com>,
<thierry.reding@gmail.com>, <jean-philippe@linaro.org>,
<jgg@nvidia.com>, <sricharan@codeaurora.org>
Cc: <yong.wu@mediatek.com>, <vdumpa@nvidia.com>,
<jonathanh@nvidia.com>, <tglx@linutronix.de>,
<shameerali.kolothum.thodi@huawei.com>,
<thunder.leizhen@huawei.com>, <christophe.jaillet@wanadoo.fr>,
<yangyingliang@huawei.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-rockchip@lists.infradead.org>,
<linux-tegra@vger.kernel.org>,
<virtualization@lists.linux-foundation.org>,
<kevin.tian@intel.com>, <quic_jjohnson@quicinc.com>
Subject: Re: [PATCH v2 00/13] iommu: Define EINVAL as device/domain incompatibility
Date: Tue, 13 Sep 2022 22:29:24 -0700 [thread overview]
Message-ID: <YyFmtOsvS9WHJEd2@Asurada-Nvidia> (raw)
In-Reply-To: <20220914051234.10006-1-nicolinc@nvidia.com>
Hi all,
On Tue, Sep 13, 2022 at 10:12:33PM -0700, Nicolin Chen wrote:
> This series is also available on Github:
> https://github.com/nicolinc/iommufd/commits/iommu_attach_dev-v2
>
> Changelog
> v2:
I just realized that the chain of this version is broken. Yet, I
think that people can still review the changes, though they may
not be grouped together. I will fix this in the next respin.
Thanks
Nicolin
WARNING: multiple messages have this Message-ID (diff)
From: Nicolin Chen <nicolinc@nvidia.com>
To: <joro@8bytes.org>, <suravee.suthikulpanit@amd.com>,
<will@kernel.org>, <robin.murphy@arm.com>, <robdclark@gmail.com>,
<dwmw2@infradead.org>, <baolu.lu@linux.intel.com>,
<agross@kernel.org>, <bjorn.andersson@linaro.org>,
<konrad.dybcio@somainline.org>, <matthias.bgg@gmail.com>,
<heiko@sntech.de>, <orsonzhai@gmail.com>,
<baolin.wang@linux.alibaba.com>, <zhang.lyra@gmail.com>,
<thierry.reding@gmail.com>, <jean-philippe@linaro.org>,
<jgg@nvidia.com>, <sricharan@codeaurora.org>
Cc: <yong.wu@mediatek.com>, <vdumpa@nvidia.com>,
<jonathanh@nvidia.com>, <tglx@linutronix.de>,
<shameerali.kolothum.thodi@huawei.com>,
<thunder.leizhen@huawei.com>, <christophe.jaillet@wanadoo.fr>,
<yangyingliang@huawei.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-rockchip@lists.infradead.org>,
<linux-tegra@vger.kernel.org>,
<virtualization@lists.linux-foundation.org>,
<kevin.tian@intel.com>, <quic_jjohnson@quicinc.com>
Subject: Re: [PATCH v2 00/13] iommu: Define EINVAL as device/domain incompatibility
Date: Tue, 13 Sep 2022 22:29:24 -0700 [thread overview]
Message-ID: <YyFmtOsvS9WHJEd2@Asurada-Nvidia> (raw)
In-Reply-To: <20220914051234.10006-1-nicolinc@nvidia.com>
Hi all,
On Tue, Sep 13, 2022 at 10:12:33PM -0700, Nicolin Chen wrote:
> This series is also available on Github:
> https://github.com/nicolinc/iommufd/commits/iommu_attach_dev-v2
>
> Changelog
> v2:
I just realized that the chain of this version is broken. Yet, I
think that people can still review the changes, though they may
not be grouped together. I will fix this in the next respin.
Thanks
Nicolin
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
WARNING: multiple messages have this Message-ID (diff)
From: Nicolin Chen <nicolinc@nvidia.com>
To: <joro@8bytes.org>, <suravee.suthikulpanit@amd.com>,
<will@kernel.org>, <robin.murphy@arm.com>, <robdclark@gmail.com>,
<dwmw2@infradead.org>, <baolu.lu@linux.intel.com>,
<agross@kernel.org>, <bjorn.andersson@linaro.org>,
<konrad.dybcio@somainline.org>, <matthias.bgg@gmail.com>,
<heiko@sntech.de>, <orsonzhai@gmail.com>,
<baolin.wang@linux.alibaba.com>, <zhang.lyra@gmail.com>,
<thierry.reding@gmail.com>, <jean-philippe@linaro.org>,
<jgg@nvidia.com>, <sricharan@codeaurora.org>
Cc: kevin.tian@intel.com, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org, yangyingliang@huawei.com,
jon@solid-run.com, iommu@lists.linux.dev,
shameerali.kolothum.thodi@huawei.com, jonathanh@nvidia.com,
linux-rockchip@lists.infradead.org,
christophe.jaillet@wanadoo.fr,
linux-arm-kernel@lists.infradead.org, thunder.leizhen@huawei.com,
linux-tegra@vger.kernel.org, linux-mediatek@lists.infradead.org,
tglx@linutronix.de, virtualization@lists.linux-foundation.org,
quic_jjohnson@quicinc.com, yong.wu@mediatek.com
Subject: Re: [PATCH v2 00/13] iommu: Define EINVAL as device/domain incompatibility
Date: Tue, 13 Sep 2022 22:29:24 -0700 [thread overview]
Message-ID: <YyFmtOsvS9WHJEd2@Asurada-Nvidia> (raw)
In-Reply-To: <20220914051234.10006-1-nicolinc@nvidia.com>
Hi all,
On Tue, Sep 13, 2022 at 10:12:33PM -0700, Nicolin Chen wrote:
> This series is also available on Github:
> https://github.com/nicolinc/iommufd/commits/iommu_attach_dev-v2
>
> Changelog
> v2:
I just realized that the chain of this version is broken. Yet, I
think that people can still review the changes, though they may
not be grouped together. I will fix this in the next respin.
Thanks
Nicolin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-09-14 5:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 5:12 [PATCH v2 00/13] iommu: Define EINVAL as device/domain incompatibility Nicolin Chen
2022-09-14 5:12 ` Nicolin Chen
2022-09-14 5:12 ` Nicolin Chen
2022-09-14 5:12 ` [PATCH v2 03/13] iommu: Add return value rules to attach_dev op Nicolin Chen
2022-09-14 5:12 ` Nicolin Chen
2022-09-14 5:12 ` Nicolin Chen
2022-09-14 5:29 ` Nicolin Chen [this message]
2022-09-14 5:29 ` [PATCH v2 00/13] iommu: Define EINVAL as device/domain incompatibility Nicolin Chen
2022-09-14 5:29 ` Nicolin Chen
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=YyFmtOsvS9WHJEd2@Asurada-Nvidia \
--to=nicolinc@nvidia.com \
--cc=agross@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=baolu.lu@linux.intel.com \
--cc=bjorn.andersson@linaro.org \
--cc=christophe.jaillet@wanadoo.fr \
--cc=dwmw2@infradead.org \
--cc=heiko@sntech.de \
--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=konrad.dybcio@somainline.org \
--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-rockchip@lists.infradead.org \
--cc=linux-tegra@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=orsonzhai@gmail.com \
--cc=quic_jjohnson@quicinc.com \
--cc=robdclark@gmail.com \
--cc=robin.murphy@arm.com \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=sricharan@codeaurora.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.