From: Nicolin Chen <nicoleotsuka@gmail.com>
To: thierry.reding@gmail.com, joro@8bytes.org
Cc: linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
jonathanh@nvidia.com, hch@infradead.org,
linux-tegra@vger.kernel.org, digetx@gmail.com
Subject: Re: [PATCH v4 0/2] iommu/tegra-smmu: Two followup changes
Date: Sat, 7 Nov 2020 00:35:39 -0800 [thread overview]
Message-ID: <20201107083538.GA24113@Asurada-Nvidia> (raw)
In-Reply-To: <20200929061325.10197-1-nicoleotsuka@gmail.com>
On Mon, Sep 28, 2020 at 11:13:23PM -0700, Nicolin Chen wrote:
> Two followup patches for tegra-smmu:
> PATCH-1 is a clean-up patch for the recently applied SWGROUP change.
> PATCH-2 fixes a potential race condition
These two changes have Acked-by and Reviewed-by for a month already.
Who can apply them?
Thanks
Nic
> Changelog
> v3->v4:
> * PATCH-2: Fixed typo in subject
> v2->v3:
> * PATCH-2: renamed "err_unlock" to "unlock"
> v1->v2:
> * Separated first two changs of V1 so they may get applied first,
> since the other three changes need some extra time to finalize.
>
> Nicolin Chen (2):
> iommu/tegra-smmu: Unwrap tegra_smmu_group_get
> iommu/tegra-smmu: Expand mutex protection range
>
> drivers/iommu/tegra-smmu.c | 53 ++++++++++++++++++--------------------
> 1 file changed, 25 insertions(+), 28 deletions(-)
>
> --
> 2.17.1
>
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Nicolin Chen <nicoleotsuka@gmail.com>
To: thierry.reding@gmail.com, joro@8bytes.org
Cc: vdumpa@nvidia.com, jonathanh@nvidia.com, digetx@gmail.com,
linux-tegra@vger.kernel.org, iommu@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, hch@infradead.org
Subject: Re: [PATCH v4 0/2] iommu/tegra-smmu: Two followup changes
Date: Sat, 7 Nov 2020 00:35:39 -0800 [thread overview]
Message-ID: <20201107083538.GA24113@Asurada-Nvidia> (raw)
In-Reply-To: <20200929061325.10197-1-nicoleotsuka@gmail.com>
On Mon, Sep 28, 2020 at 11:13:23PM -0700, Nicolin Chen wrote:
> Two followup patches for tegra-smmu:
> PATCH-1 is a clean-up patch for the recently applied SWGROUP change.
> PATCH-2 fixes a potential race condition
These two changes have Acked-by and Reviewed-by for a month already.
Who can apply them?
Thanks
Nic
> Changelog
> v3->v4:
> * PATCH-2: Fixed typo in subject
> v2->v3:
> * PATCH-2: renamed "err_unlock" to "unlock"
> v1->v2:
> * Separated first two changs of V1 so they may get applied first,
> since the other three changes need some extra time to finalize.
>
> Nicolin Chen (2):
> iommu/tegra-smmu: Unwrap tegra_smmu_group_get
> iommu/tegra-smmu: Expand mutex protection range
>
> drivers/iommu/tegra-smmu.c | 53 ++++++++++++++++++--------------------
> 1 file changed, 25 insertions(+), 28 deletions(-)
>
> --
> 2.17.1
>
next prev parent reply other threads:[~2020-11-07 8:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 6:13 [PATCH v4 0/2] iommu/tegra-smmu: Two followup changes Nicolin Chen
2020-09-29 6:13 ` Nicolin Chen
2020-09-29 6:13 ` [PATCH v4 1/2] iommu/tegra-smmu: Unwrap tegra_smmu_group_get Nicolin Chen
2020-09-29 6:13 ` Nicolin Chen
2020-09-29 17:41 ` Dmitry Osipenko
2020-09-29 17:41 ` Dmitry Osipenko
2020-10-03 14:27 ` Dmitry Osipenko
2020-10-03 14:27 ` Dmitry Osipenko
2020-10-08 9:55 ` Thierry Reding
2020-10-08 9:55 ` Thierry Reding
2020-09-29 6:13 ` [PATCH v4 2/2] iommu/tegra-smmu: Expand mutex protection range Nicolin Chen
2020-09-29 6:13 ` Nicolin Chen
2020-09-29 17:42 ` Dmitry Osipenko
2020-09-29 17:42 ` Dmitry Osipenko
2020-09-30 0:31 ` Nicolin Chen
2020-09-30 0:31 ` Nicolin Chen
2020-10-03 14:28 ` Dmitry Osipenko
2020-10-03 14:28 ` Dmitry Osipenko
2020-10-08 9:56 ` Thierry Reding
2020-10-08 9:56 ` Thierry Reding
2020-11-07 8:35 ` Nicolin Chen [this message]
2020-11-07 8:35 ` [PATCH v4 0/2] iommu/tegra-smmu: Two followup changes 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=20201107083538.GA24113@Asurada-Nvidia \
--to=nicoleotsuka@gmail.com \
--cc=digetx@gmail.com \
--cc=hch@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jonathanh@nvidia.com \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@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.