From: Joerg Roedel <joro@8bytes.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Magnus Damm <damm+renesas@opensource.se>,
Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
iommu@lists.linux-foundation.org,
linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/6] iommu/ipmmu-vmsa: Suspend/resume support and assorted cleanups
Date: Mon, 3 Jun 2019 12:18:37 +0200 [thread overview]
Message-ID: <20190603101836.GI12745@8bytes.org> (raw)
In-Reply-To: <20190527115253.2114-1-geert+renesas@glider.be>
On Mon, May 27, 2019 at 01:52:47PM +0200, Geert Uytterhoeven wrote:
> Geert Uytterhoeven (6):
> iommu/ipmmu-vmsa: Link IOMMUs and devices in sysfs
> iommu/ipmmu-vmsa: Prepare to handle 40-bit error addresses
> iommu/ipmmu-vmsa: Make IPMMU_CTX_MAX unsigned
> iommu/ipmmu-vmsa: Move num_utlbs to SoC-specific features
> iommu/ipmmu-vmsa: Extract hardware context initialization
> iommu/ipmmu-vmsa: Add suspend/resume support
Applied, thanks Geert.
prev parent reply other threads:[~2019-06-03 10:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-27 11:52 [PATCH v4 0/6] iommu/ipmmu-vmsa: Suspend/resume support and assorted cleanups Geert Uytterhoeven
2019-05-27 11:52 ` [PATCH v4 1/6] iommu/ipmmu-vmsa: Link IOMMUs and devices in sysfs Geert Uytterhoeven
2019-05-27 11:52 ` [PATCH v4 2/6] iommu/ipmmu-vmsa: Prepare to handle 40-bit error addresses Geert Uytterhoeven
2019-05-27 11:52 ` [PATCH v4 3/6] iommu/ipmmu-vmsa: Make IPMMU_CTX_MAX unsigned Geert Uytterhoeven
2019-05-27 11:52 ` [PATCH v4 4/6] iommu/ipmmu-vmsa: Move num_utlbs to SoC-specific features Geert Uytterhoeven
2019-05-27 11:52 ` [PATCH v4 5/6] iommu/ipmmu-vmsa: Extract hardware context initialization Geert Uytterhoeven
2019-05-27 11:52 ` [PATCH v4 6/6] iommu/ipmmu-vmsa: Add suspend/resume support Geert Uytterhoeven
2019-06-03 10:18 ` Joerg Roedel [this message]
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=20190603101836.GI12745@8bytes.org \
--to=joro@8bytes.org \
--cc=damm+renesas@opensource.se \
--cc=geert+renesas@glider.be \
--cc=iommu@lists.linux-foundation.org \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.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