From: heiko@sntech.de (Heiko Stübner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] Rockchip IOMMU driver and devicetree bindings
Date: Thu, 23 Oct 2014 18:23 +0200 [thread overview]
Message-ID: <2804227.ziAnEUAn0E@diego> (raw)
In-Reply-To: <CAGS+omB+si1J-gjyvyjJF0x=QBTyPyNKbqyV0QM=sKNo9zecDw@mail.gmail.com>
Am Freitag, 24. Oktober 2014, 00:11:06 schrieb Daniel Kurtz:
> On Wed, Oct 22, 2014 at 11:20 PM, Joerg Roedel <joro@8bytes.org> wrote:
> > On Wed, Oct 01, 2014 at 06:20:40PM +0800, Daniel Kurtz wrote:
> > > Add a driver and devicetree bindings for the IOMMU found in Rockchip
> >
> > RK3288
> >
> > > SoCs.
> > >
> > > Daniel Kurtz (3):
> > > iommu/rockchip: rk3288 iommu driver
> > > dt-bindings: iommu: Add documentation for rockchip iommu
> > > ARM: dts: rk3288: add VOP iommu nodes
> > >
> > > .../devicetree/bindings/iommu/rockchip,iommu.txt | 26 +
> > > arch/arm/boot/dts/rk3288.dtsi | 18 +
> > > drivers/iommu/Kconfig | 11 +
> > > drivers/iommu/Makefile | 1 +
> > > drivers/iommu/rockchip-iommu.c | 924
> >
> > +++++++++++++++++++++
> >
> > > 5 files changed, 980 insertions(+)
> > > create mode 100644
> >
> > Documentation/devicetree/bindings/iommu/rockchip,iommu.txt
> >
> > > create mode 100644 drivers/iommu/rockchip-iommu.c
> >
> > Please make sure you also get Acks for the DT bindings. With that and
> > the issue I mentioned in the other email fixed, I will apply these
> > patches?
>
> Hi Joerg,
>
> Thanks for your reviews.
> Can you help me get these DT bindings Acked?
> AFAICT, the DT maintainers are CC'ed on this patch, I'm not sure what else
> to do.
I think the generally accepted way is, to give the dt maintainers an
appropriate amount of time [0] to complain and assume an implicit ack if no
complaint arrives.
This is especially true, as the dt-binding for the iommu itself does not even
introduce any new properties and simply uses widely established ones.
As a sidenote ... I'd like to take the dts changes in patch 3, once Joerg
takes patches 1 and 2.
Heiko
[0] 3 weeks seems to be the most widely used timespan
prev parent reply other threads:[~2014-10-23 16:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 10:20 [PATCH 0/3] Rockchip IOMMU driver and devicetree bindings Daniel Kurtz
2014-10-01 10:20 ` [PATCH 1/3] iommu/rockchip: rk3288 iommu driver Daniel Kurtz
2014-10-07 17:05 ` Grant Grundler
2014-10-01 10:20 ` [PATCH 2/3] dt-bindings: iommu: Add documentation for rockchip iommu Daniel Kurtz
2014-10-01 10:20 ` [PATCH 3/3] ARM: dts: rk3288: add VOP iommu nodes Daniel Kurtz
2014-10-22 15:20 ` [PATCH 0/3] Rockchip IOMMU driver and devicetree bindings Joerg Roedel
2014-10-23 16:15 ` Daniel Kurtz
[not found] ` <CAGS+omB+si1J-gjyvyjJF0x=QBTyPyNKbqyV0QM=sKNo9zecDw@mail.gmail.com>
2014-10-23 16:23 ` Heiko Stübner [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=2804227.ziAnEUAn0E@diego \
--to=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.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).