[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160802220035.GB15995@brightrain.aerifal.cx>
Date: Tue, 2 Aug 2016 18:00:35 -0400
From: Rich Felker <dalias@...c.org>
To: Rob Herring <robh@...nel.org>
Cc: devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-spi@...r.kernel.org, linux-sh@...r.kernel.org,
Mark Rutland <mark.rutland@....com>,
Mark Brown <broonie@...nel.org>
Subject: Re: [PATCH v4 1/2] of: add J-Core SPI master bindings
On Fri, Jul 29, 2016 at 03:58:38PM -0500, Rob Herring wrote:
> On Tue, May 17, 2016 at 11:19:25PM +0000, Rich Felker wrote:
> > Signed-off-by: Rich Felker <dalias@...c.org>
> > ---
> > .../devicetree/bindings/spi/jcore,spi.txt | 30 ++++++++++++++++++++++
> > 1 file changed, 30 insertions(+)
> > create mode 100644 Documentation/devicetree/bindings/spi/jcore,spi.txt
>
> Acked-by: Rob Herring <robh@...nel.org>
Thanks. Since I switched to to using the clk framework rather than a
clock-frequency property (at Mark Brown's suggestion/request), I'll be
submitting one more version for your review.
After that, who should be responsible for upstreaming this and the
other binding patches? You, me, or the subsystem maintainers that the
drivers are going through?
Rich
Powered by blists - more mailing lists