From: Dmitry Osipenko <digetx@gmail.com>
To: Nicolin Chen <nicoleotsuka@gmail.com>, joro@8bytes.org
Cc: linux-kernel@vger.kernel.org, jonathanh@nvidia.com,
iommu@lists.linux-foundation.org, thierry.reding@gmail.com,
linux-tegra@vger.kernel.org, Will Deacon <will@kernel.org>
Subject: Re: [PATCH RESEND 0/5] iommu/tegra-smmu: Some pending reviewed changes
Date: Wed, 25 Nov 2020 02:05:14 +0300 [thread overview]
Message-ID: <68237d7c-12f7-3053-2e79-75b7e95f0af3@gmail.com> (raw)
In-Reply-To: <20201124212100.GA32108@Asurada-Nvidia>
25.11.2020 00:21, Nicolin Chen пишет:
> Hi Joerg,
>
> These five patches were acked by Thierry and acked-n-tested by
> Dmitry a while ago. Would it be possible for you to apply them?
>
> Thanks!
Hi,
You probably should try to ping Will Deacon.
https://lkml.org/lkml/2020/11/17/243
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2020-11-24 23:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-11 22:21 [PATCH RESEND 0/5] iommu/tegra-smmu: Some pending reviewed changes Nicolin Chen
2020-11-11 22:21 ` [PATCH RESEND 1/5] iommu/tegra-smmu: Unwrap tegra_smmu_group_get Nicolin Chen
2020-11-11 22:21 ` [PATCH RESEND 2/5] iommu/tegra-smmu: Expand mutex protection range Nicolin Chen
2020-11-11 22:21 ` [PATCH RESEND 3/5] iommu/tegra-smmu: Use fwspec in tegra_smmu_(de)attach_dev Nicolin Chen
2020-11-20 16:23 ` Thierry Reding
2020-11-11 22:21 ` [PATCH RESEND 4/5] iommu/tegra-smmu: Rework tegra_smmu_probe_device() Nicolin Chen
2020-11-20 16:25 ` Thierry Reding
2020-11-11 22:21 ` [PATCH RESEND 5/5] iommu/tegra-smmu: Add PCI support Nicolin Chen
2020-11-20 16:26 ` Thierry Reding
2020-11-24 21:21 ` [PATCH RESEND 0/5] iommu/tegra-smmu: Some pending reviewed changes Nicolin Chen
2020-11-24 23:05 ` Dmitry Osipenko [this message]
2020-11-24 23:12 ` Nicolin Chen
2020-11-25 9:55 ` Will Deacon
2020-11-25 10:08 ` 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=68237d7c-12f7-3053-2e79-75b7e95f0af3@gmail.com \
--to=digetx@gmail.com \
--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=will@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).