From: Alex Williamson <alex.williamson@redhat.com>
To: Simon Horman <horms+renesas@verge.net.au>
Cc: Joerg Roedel <joro@8bytes.org>,
linux-renesas-soc@vger.kernel.org,
iommu@lists.linux-foundation.org,
Magnus Damm <magnus.damm@gmail.com>
Subject: Re: [PATCH 0/2] iommu/ipmmu-vmsa: r8a779(70|95) support
Date: Mon, 6 Nov 2017 12:22:01 -0700 [thread overview]
Message-ID: <20171106122201.77d640e5@t450s.home> (raw)
In-Reply-To: <20171101103423.7334-1-horms+renesas@verge.net.au>
On Wed, 1 Nov 2017 11:34:21 +0100
Simon Horman <horms+renesas@verge.net.au> wrote:
> Update Update the IPMMU DT binding documentation and driver implementation
> to support the r8a77970 (R-Car V3M) and r8a77995 (R-Car D3).
>
> Based on work for r8a7796 by Magnus Damm.
>
> Patches based on:
> * iommu/next
> * [PATCH v5 00/09] iommu/ipmmu-vmsa: r8a7795 support V5
> * [PATCH v4 0/3] iommu/ipmmu-vmsa: r8a7796 support V4
> (fuzz when applying 3/3)
This last dependent patch series hasn't had any comments or updates
since June. Do I take it from Simon's new patches here that it's still
relevant and desired? Perhaps it was simply missed and nobody bothered
to re-send it? Thanks,
Alex
> Simon Horman (2):
> iommu/ipmmu-vmsa: Add r8a779(70|95) DT bindings
> iommu/ipmmu-vmsa: Hook up r8a779(70|95) DT matching code
>
> .../devicetree/bindings/iommu/renesas,ipmmu-vmsa.txt | 2 ++
> drivers/iommu/ipmmu-vmsa.c | 12 ++++++++++++
> 2 files changed, 14 insertions(+)
>
next prev parent reply other threads:[~2017-11-06 19:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-01 10:34 [PATCH 0/2] iommu/ipmmu-vmsa: r8a779(70|95) support Simon Horman
2017-11-01 10:34 ` [PATCH 1/2] iommu/ipmmu-vmsa: Add r8a779(70|95) DT bindings Simon Horman
2017-11-07 8:29 ` Geert Uytterhoeven
2017-11-01 10:34 ` [PATCH 2/2] iommu/ipmmu-vmsa: Hook up r8a779(70|95) DT matching code Simon Horman
2017-11-07 8:31 ` Geert Uytterhoeven
2017-11-06 19:22 ` Alex Williamson [this message]
2017-11-10 8:38 ` [PATCH 0/2] iommu/ipmmu-vmsa: r8a779(70|95) support Simon Horman
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=20171106122201.77d640e5@t450s.home \
--to=alex.williamson@redhat.com \
--cc=horms+renesas@verge.net.au \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.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;
as well as URLs for NNTP newsgroup(s).