From: Thierry Reding <thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
Cc: Hiroshi Doyu <hdoyu-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
Jonathan Hunter
<jonathanh-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
Robin Murphy <robin.murphy-5wv7dgnIgG8@public.gmane.org>,
iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 0/2] iommu/tegra*: Add support for struct iommu_device
Date: Thu, 17 Aug 2017 15:58:03 +0200 [thread overview]
Message-ID: <20170817135803.GG6854@ulmo> (raw)
In-Reply-To: <1502317752-8792-1-git-send-email-joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 867 bytes --]
On Thu, Aug 10, 2017 at 12:29:10AM +0200, Joerg Roedel wrote:
> Hi,
>
> here are two patches to add support for 'struct iommu_device'
> to the tegra iommu-drivers. This will make the iommu-core
> code aware of the hardware iommus that a driver manages.
>
> It will also add the iommus to sysfs and link them to the
> devices managed by them.
>
> The patches apply on-top of Robin's iommu-group patches.
>
> Please review.
>
> Regards,
>
> Joerg
>
> Joerg Roedel (2):
> iommu/tegra: Add support for struct iommu_device
> iommu/tegra-gart: Add support for struct iommu_device
>
> drivers/iommu/tegra-gart.c | 26 ++++++++++++++++++++++++++
> drivers/iommu/tegra-smmu.c | 25 +++++++++++++++++++++++++
> 2 files changed, 51 insertions(+)
The series:
Acked-by: Thierry Reding <treding-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Thierry Reding <thierry.reding@gmail.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: Hiroshi Doyu <hdoyu@nvidia.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Robin Murphy <robin.murphy@arm.com>,
iommu@lists.linux-foundation.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] iommu/tegra*: Add support for struct iommu_device
Date: Thu, 17 Aug 2017 15:58:03 +0200 [thread overview]
Message-ID: <20170817135803.GG6854@ulmo> (raw)
In-Reply-To: <1502317752-8792-1-git-send-email-joro@8bytes.org>
[-- Attachment #1: Type: text/plain, Size: 838 bytes --]
On Thu, Aug 10, 2017 at 12:29:10AM +0200, Joerg Roedel wrote:
> Hi,
>
> here are two patches to add support for 'struct iommu_device'
> to the tegra iommu-drivers. This will make the iommu-core
> code aware of the hardware iommus that a driver manages.
>
> It will also add the iommus to sysfs and link them to the
> devices managed by them.
>
> The patches apply on-top of Robin's iommu-group patches.
>
> Please review.
>
> Regards,
>
> Joerg
>
> Joerg Roedel (2):
> iommu/tegra: Add support for struct iommu_device
> iommu/tegra-gart: Add support for struct iommu_device
>
> drivers/iommu/tegra-gart.c | 26 ++++++++++++++++++++++++++
> drivers/iommu/tegra-smmu.c | 25 +++++++++++++++++++++++++
> 2 files changed, 51 insertions(+)
The series:
Acked-by: Thierry Reding <treding@nvidia.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-08-17 13:58 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-09 22:29 [PATCH 0/2] iommu/tegra*: Add support for struct iommu_device Joerg Roedel
2017-08-09 22:29 ` Joerg Roedel
2017-08-09 22:29 ` [PATCH 1/2] iommu/tegra: " Joerg Roedel
[not found] ` <1502317752-8792-2-git-send-email-joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2017-08-18 12:47 ` Thierry Reding
2017-08-18 12:47 ` Thierry Reding
2017-08-30 11:04 ` Jon Hunter
2017-08-30 11:04 ` Jon Hunter
2017-08-30 12:09 ` Joerg Roedel
[not found] ` <20170830120902.kqtxh2ls4ob7xpwy-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2017-08-30 14:22 ` Jon Hunter
2017-08-30 14:22 ` Jon Hunter
[not found] ` <c6ee1ce0-7193-be63-c84d-73795c727d26-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2017-08-30 15:30 ` Joerg Roedel
2017-08-30 15:30 ` Joerg Roedel
2017-08-30 15:30 ` Joerg Roedel
[not found] ` <20170830153034.GK19533-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2017-08-30 16:53 ` Jon Hunter
2017-08-30 16:53 ` Jon Hunter
2017-08-31 10:23 ` Jon Hunter
2017-08-31 10:23 ` Jon Hunter
[not found] ` <1502317752-8792-1-git-send-email-joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2017-08-09 22:29 ` [PATCH 2/2] iommu/tegra-gart: " Joerg Roedel
2017-08-09 22:29 ` Joerg Roedel
[not found] ` <1502317752-8792-3-git-send-email-joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2017-08-16 22:21 ` Dmitry Osipenko
2017-08-16 22:21 ` Dmitry Osipenko
[not found] ` <66711b72-455f-8ec1-e6f7-5946480dde14-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-08-17 13:52 ` Thierry Reding
2017-08-17 13:52 ` Thierry Reding
2017-08-17 17:17 ` Dmitry Osipenko
2017-08-18 12:47 ` Thierry Reding
2017-08-17 13:58 ` Thierry Reding [this message]
2017-08-17 13:58 ` [PATCH 0/2] iommu/tegra*: " Thierry Reding
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=20170817135803.GG6854@ulmo \
--to=thierry.reding-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=hdoyu-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=jonathanh-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=robin.murphy-5wv7dgnIgG8@public.gmane.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.