From: Thierry Reding <thierry.reding@gmail.com>
To: Rob Herring <robh@kernel.org>
Cc: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
linux-pwm@vger.kernel.org, devicetree@vger.kernel.org,
Mark Rutland <mark.rutland@arm.com>,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: pwm: renesas: pwm-rcar: document R8A779{7|8}0 bindings
Date: Tue, 16 Oct 2018 12:46:51 +0200 [thread overview]
Message-ID: <20181016104651.GA8852@ulmo> (raw)
In-Reply-To: <20181015185713.GA15344@bogus>
[-- Attachment #1: Type: text/plain, Size: 1021 bytes --]
On Mon, Oct 15, 2018 at 01:57:13PM -0500, Rob Herring wrote:
> On Fri, Oct 12, 2018 at 01:21:14PM +0200, Thierry Reding wrote:
> > On Mon, Oct 01, 2018 at 10:57:39PM +0300, Sergei Shtylyov wrote:
> > > Document the R-Car V3{M|H} (R8A779{7|8}0) SoC in the Renesas R-Car PWM
> > > bindings. R8A77970's hardware is a generic R-Car gen3 PWM, while R8A77980
> > > has an extra error injection register...
> > >
> > > Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
> > >
> > > ---
> > > This patch is against the 'for-next' branch of Thierry Reding's 'linux-pwm.git'
> > > repo.
> > >
> > > Documentation/devicetree/bindings/pwm/renesas,pwm-rcar.txt | 2 ++
> > > 1 file changed, 2 insertions(+)
> >
> > Applied, thanks.
>
> Some reason your tree isn't updated for linux-next?
No particular reason, I just had not pushed it out yet because the build
tests were taking longer than expected and I had to clean up a couple of
minor things.
It's pushed out now.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2018-10-16 10:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-01 19:57 [PATCH] dt-bindings: pwm: renesas: pwm-rcar: document R8A779{7|8}0 bindings Sergei Shtylyov
2018-10-02 7:14 ` Geert Uytterhoeven
2018-10-04 9:30 ` Simon Horman
2018-10-12 11:21 ` Thierry Reding
2018-10-15 18:57 ` Rob Herring
2018-10-16 10:46 ` Thierry Reding [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=20181016104651.GA8852@ulmo \
--to=thierry.reding@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh@kernel.org \
--cc=sergei.shtylyov@cogentembedded.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 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.