From: Biju Das <biju.das@bp.renesas.com>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Simon Horman <horms@verge.net.au>,
Chris Paterson <Chris.Paterson2@renesas.com>,
Marian-Cristian Rotariu
<marian-cristian.rotariu.rb@bp.renesas.com>,
Fabrizio Castro <fabrizio.castro@bp.renesas.com>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>
Subject: RE: [PATCH] clock: renesas: cpg-mssr: Fix the typo
Date: Wed, 18 Dec 2019 12:49:23 +0000 [thread overview]
Message-ID: <OSBPR01MB2103DDF07C530B24DCD2BE4BB8530@OSBPR01MB2103.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <2368e2c8-7f80-ec22-2c9f-4f719ab347dc@cogentembedded.com>
Hi Sergei,
Thanks for the feedback.
> Subject: Re: [PATCH] clock: renesas: cpg-mssr: Fix the typo
>
> On 18.12.2019 14:09, Biju Das wrote:
>
> > This patch fixes the typo %s/r8a774a1/r8a774b1/.
> >
> > Fixes: 1000393 ("dt-bindings: clock: renesas: cpg-mssr: Document r8a774b1
>
> SHA1 should have at least 12 digits.
>
Ok will do.
> > binding")
>
> And never break up the tag lines please.
Do you mean , do the changes like below and ignore check patch warnings? Is it acceptable to everyone?
Fixes: 10003938a0c64c2f0d89 ("dt-bindings: clock: renesas: cpg-mssr: Document r8a774b1 binding")
> > Signed-off-by: Biju Das <biju.das@bp.renesas.com>
> [...]
>
> MBR, Sergei
next prev parent reply other threads:[~2019-12-18 12:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 11:09 [PATCH] clock: renesas: cpg-mssr: Fix the typo Biju Das
2019-12-18 12:27 ` Sergei Shtylyov
2019-12-18 12:49 ` Biju Das [this message]
2019-12-18 18:01 ` Sergei Shtylyov
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=OSBPR01MB2103DDF07C530B24DCD2BE4BB8530@OSBPR01MB2103.jpnprd01.prod.outlook.com \
--to=biju.das@bp.renesas.com \
--cc=Chris.Paterson2@renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=fabrizio.castro@bp.renesas.com \
--cc=geert+renesas@glider.be \
--cc=horms@verge.net.au \
--cc=linux-clk@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=marian-cristian.rotariu.rb@bp.renesas.com \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@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 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).