From: Will Deacon <will@kernel.org>
To: Nicolin Chen <nicoleotsuka@gmail.com>
Cc: linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
linux-tegra@vger.kernel.org, jonathanh@nvidia.com,
vdumpa@nvidia.com, thierry.reding@gmail.com, joro@8bytes.org
Subject: Re: [PATCH RESEND v2 0/5] iommu/tegra-smmu: Some pending reviewed changes
Date: Wed, 25 Nov 2020 11:03:50 +0000 [thread overview]
Message-ID: <20201125110349.GA15239@willie-the-truck> (raw)
In-Reply-To: <20201125101013.14953-1-nicoleotsuka@gmail.com>
On Wed, Nov 25, 2020 at 02:10:08AM -0800, Nicolin Chen wrote:
> Changelog
> v1->v2:
> * Added Thierry's acks to PATCH-3~5
>
> This is a merged set of resend for previously two series of patches
> that were reviewed/acked a month ago yet have not got applied.
Thanks, and sorry I missed these (I'm doing my best). I'll queue the
lot for 5.11.
Will
next prev parent reply other threads:[~2020-11-25 11:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 10:10 Nicolin Chen
2020-11-25 10:10 ` [PATCH RESEND v2 1/5] iommu/tegra-smmu: Unwrap tegra_smmu_group_get Nicolin Chen
2020-11-25 10:10 ` [PATCH RESEND v2 2/5] iommu/tegra-smmu: Expand mutex protection range Nicolin Chen
2020-11-25 10:10 ` [PATCH RESEND v2 3/5] iommu/tegra-smmu: Use fwspec in tegra_smmu_(de)attach_dev Nicolin Chen
2020-11-25 10:10 ` [PATCH RESEND v2 4/5] iommu/tegra-smmu: Rework tegra_smmu_probe_device() Nicolin Chen
2021-02-04 11:10 ` Guillaume Tucker
2021-02-05 5:24 ` Nicolin Chen
2021-02-05 9:45 ` Nicolin Chen
2021-02-06 13:40 ` Guillaume Tucker
2021-02-10 8:20 ` Nicolin Chen
2021-02-11 15:50 ` Guillaume Tucker
2021-02-18 10:35 ` Nicolin Chen
2021-02-18 20:38 ` Guillaume Tucker
2020-11-25 10:10 ` [PATCH RESEND v2 5/5] iommu/tegra-smmu: Add PCI support Nicolin Chen
2020-11-25 11:03 ` Will Deacon [this message]
2020-11-25 14:05 ` [PATCH RESEND v2 0/5] iommu/tegra-smmu: Some pending reviewed changes Will Deacon
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=20201125110349.GA15239@willie-the-truck \
--to=will@kernel.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=nicoleotsuka@gmail.com \
--cc=thierry.reding@gmail.com \
--cc=vdumpa@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®