From: Joerg Roedel <joro@8bytes.org>
To: Nicolin Chen <nicoleotsuka@gmail.com>
Cc: guillaume.tucker@collabora.com, iommu@lists.linux-foundation.org,
jonathanh@nvidia.com, thierry.reding@gmail.com,
linux-tegra@vger.kernel.org, digetx@gmail.com, will@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iommu/tegra-smmu: Fix mc errors on tegra124-nyan
Date: Thu, 4 Mar 2021 13:21:31 +0100 [thread overview]
Message-ID: <20210304122131.GC26414@8bytes.org> (raw)
In-Reply-To: <20210218220702.1962-1-nicoleotsuka@gmail.com>
On Thu, Feb 18, 2021 at 02:07:02PM -0800, Nicolin Chen wrote:
> drivers/iommu/tegra-smmu.c | 72 +++++++++++++++++++++++++++++++++++++-
> 1 file changed, 71 insertions(+), 1 deletion(-)
Applied for v5.12, thanks.
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Joerg Roedel <joro@8bytes.org>
To: Nicolin Chen <nicoleotsuka@gmail.com>
Cc: thierry.reding@gmail.com, will@kernel.org,
guillaume.tucker@collabora.com, vdumpa@nvidia.com,
jonathanh@nvidia.com, digetx@gmail.com,
linux-tegra@vger.kernel.org, iommu@lists.linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iommu/tegra-smmu: Fix mc errors on tegra124-nyan
Date: Thu, 4 Mar 2021 13:21:31 +0100 [thread overview]
Message-ID: <20210304122131.GC26414@8bytes.org> (raw)
In-Reply-To: <20210218220702.1962-1-nicoleotsuka@gmail.com>
On Thu, Feb 18, 2021 at 02:07:02PM -0800, Nicolin Chen wrote:
> drivers/iommu/tegra-smmu.c | 72 +++++++++++++++++++++++++++++++++++++-
> 1 file changed, 71 insertions(+), 1 deletion(-)
Applied for v5.12, thanks.
next prev parent reply other threads:[~2021-03-04 12:29 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-18 22:07 [PATCH] iommu/tegra-smmu: Fix mc errors on tegra124-nyan Nicolin Chen
2021-02-18 22:07 ` Nicolin Chen
2021-02-20 5:16 ` Dmitry Osipenko
2021-02-20 5:16 ` Dmitry Osipenko
2021-02-23 2:13 ` Nicolin Chen
2021-02-23 2:13 ` Nicolin Chen
2021-02-23 5:10 ` Dmitry Osipenko
2021-02-23 5:10 ` Dmitry Osipenko
2021-02-25 6:27 ` Nicolin Chen
2021-02-25 6:27 ` Nicolin Chen
2021-02-27 9:59 ` Dmitry Osipenko
2021-02-27 9:59 ` Dmitry Osipenko
2021-03-02 23:08 ` Nicolin Chen
2021-03-02 23:08 ` Nicolin Chen
2021-03-03 9:47 ` Dmitry Osipenko
2021-03-03 9:47 ` Dmitry Osipenko
2021-03-28 15:25 ` Dmitry Osipenko
2021-03-28 15:25 ` Dmitry Osipenko
2021-03-28 15:36 ` Dmitry Osipenko
2021-03-28 15:36 ` Dmitry Osipenko
2021-02-22 13:15 ` Guillaume Tucker
2021-02-22 13:15 ` Guillaume Tucker
2021-03-03 18:26 ` Thierry Reding
2021-03-03 18:26 ` Thierry Reding
2021-03-04 12:21 ` Joerg Roedel [this message]
2021-03-04 12:21 ` Joerg Roedel
2021-03-10 19:13 ` Dmitry Osipenko
2021-03-10 19:13 ` Dmitry Osipenko
2021-03-10 20:22 ` Dmitry Osipenko
2021-03-10 20:22 ` Dmitry Osipenko
2021-03-10 22:17 ` Nicolin Chen
2021-03-10 22:17 ` Nicolin Chen
2021-03-11 12:06 ` Dmitry Osipenko
2021-03-11 12:06 ` Dmitry Osipenko
2021-03-12 1:09 ` Nicolin Chen
2021-03-12 1:09 ` 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=20210304122131.GC26414@8bytes.org \
--to=joro@8bytes.org \
--cc=digetx@gmail.com \
--cc=guillaume.tucker@collabora.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jonathanh@nvidia.com \
--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 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.