From: Rob Herring <robh@kernel.org>
To: Biju Das <biju.das.jz@bp.renesas.com>
Cc: "Thierry Reding" <thierry.reding@gmail.com>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
linux-pwm@vger.kernel.org, devicetree@vger.kernel.org,
"Geert Uytterhoeven" <geert+renesas@glider.be>,
"Chris Paterson" <chris.paterson2@renesas.com>,
"Prabhakar Mahadev Lad" <prabhakar.mahadev-lad.rj@bp.renesas.com>,
linux-renesas-soc@vger.kernel.org
Subject: Re: [DO NOT APPLY PATCH v3 1/3] dt-bindings: pwm: Add RZ/G2L GPT binding
Date: Tue, 20 Dec 2022 11:47:38 -0600 [thread overview]
Message-ID: <20221220174738.GA800802-robh@kernel.org> (raw)
In-Reply-To: <20221215205843.4074504-2-biju.das.jz@bp.renesas.com>
On Thu, Dec 15, 2022 at 08:58:41PM +0000, Biju Das wrote:
> Add device tree bindings for the General PWM Timer (GPT).
>
> Signed-off-by: Biju Das <biju.das.jz@bp.renesas.com>
> Reviewed-by: Rob Herring <robh@kernel.org>
> ---
> sending[1] to avoid bot error for the next patch.
Don't do that. The correct thing to do is note the dependency in the
patch with the dependency (after '---'). The bot will read that and
decide to not send a failure email to you. The bot doesn't read cover
letters.
Rob
next prev parent reply other threads:[~2022-12-20 17:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 20:58 [PATCH v3 0/3] Add support for linking gpt with poeg Biju Das
2022-12-15 20:58 ` [DO NOT APPLY PATCH v3 1/3] dt-bindings: pwm: Add RZ/G2L GPT binding Biju Das
2022-12-20 17:47 ` Rob Herring [this message]
2023-01-09 14:53 ` Biju Das
2022-12-15 20:58 ` [PATCH v3 2/3] dt-bindings: pwm: rzg2l-gpt: Document renesas,poegs property Biju Das
2022-12-20 17:48 ` Rob Herring
2022-12-15 20:58 ` [PATCH v3 3/3] pwm: rzg2l-gpt: Add support for gpt linking with poeg Biju Das
2023-02-01 15:53 ` Uwe Kleine-König
2023-02-28 12:10 ` Biju Das
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=20221220174738.GA800802-robh@kernel.org \
--to=robh@kernel.org \
--cc=biju.das.jz@bp.renesas.com \
--cc=chris.paterson2@renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--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 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.