devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Rob Herring <robh@kernel.org>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	linux-kernel@vger.kernel.org, linux-pwm@vger.kernel.org,
	"Rob Herring" <robh+dt@kernel.org>,
	devicetree@vger.kernel.org, "Lee Jones" <lee.jones@linaro.org>,
	"Laurent Pinchart" <laurent.pinchart+renesas@ideasonboard.com>,
	"Thierry Reding" <thierry.reding@gmail.com>,
	"Geert Uytterhoeven" <geert+renesas@glider.be>
Subject: Re: [PATCH] dt-bindings: pwm: tpu: Add R-Car M3-W+ device tree bindings
Date: Tue, 12 Oct 2021 14:02:15 +0200	[thread overview]
Message-ID: <YWV5R1dqpvnPFim5@kunai> (raw)
In-Reply-To: <YTjAGLlLvUOF4eO9@robh.at.kernel.org>

[-- Attachment #1: Type: text/plain, Size: 536 bytes --]

Hi Rob,

> > Add device tree bindings for TPU found on R-Car M3-W+ SoCs.
> > 
> > Reported-by: Geert Uytterhoeven <geert+renesas@glider.be>
> > Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
> > ---
> >  Documentation/devicetree/bindings/pwm/renesas,tpu-pwm.yaml | 1 +
> >  1 file changed, 1 insertion(+)
> > 
> 
> Acked-by: Rob Herring <robh@kernel.org>

could you apply it, please? Looking at git history, the YAML changes
for PWM went through your tree.

Thanks and have a nice week,

   Wolfram


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-10-12 12:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-06  9:45 [PATCH] dt-bindings: pwm: tpu: Add R-Car M3-W+ device tree bindings Wolfram Sang
2021-09-06  9:46 ` Geert Uytterhoeven
2021-09-08 13:52 ` Rob Herring
2021-10-12 12:02   ` Wolfram Sang [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-10-27 12:29 Geert Uytterhoeven
2021-10-27 22:39 ` Laurent Pinchart
2021-10-29 16:02 ` Uwe Kleine-König
2021-11-01 16:00 ` Kieran Bingham

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=YWV5R1dqpvnPFim5@kunai \
    --to=wsa+renesas@sang-engineering.com \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=laurent.pinchart+renesas@ideasonboard.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pwm@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=robh@kernel.org \
    --cc=thierry.reding@gmail.com \
    --cc=u.kleine-koenig@pengutronix.de \
    /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).