From: Rob Herring <robh@kernel.org>
To: Biju Das <biju.das@bp.renesas.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
Fabrizio Castro <fabrizio.castro@bp.renesas.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
devicetree@vger.kernel.org, Simon Horman <horms@verge.net.au>,
Chris Paterson <Chris.Paterson2@renesas.com>,
"open list:MEDIA DRIVERS FOR RENESAS - FCP"
<linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH v2 4/5] clk: renesas: Add r8a774a1 CPG Core Clock Definitions
Date: Fri, 10 Aug 2018 09:40:23 -0600 [thread overview]
Message-ID: <CAL_Jsq+ApABam=zc-peomPd-7hZ4zf0zvd=vPzdUmTXP80MXog@mail.gmail.com> (raw)
In-Reply-To: <OSBPR01MB21036ED37D495C23FE0ABFB9B8240@OSBPR01MB2103.jpnprd01.prod.outlook.com>
On Fri, Aug 10, 2018 at 1:35 AM Biju Das <biju.das@bp.renesas.com> wrote:
>
> Hi Rob,
>
>
> > Subject: Re: [PATCH v2 4/5] clk: renesas: Add r8a774a1 CPG Core Clock
> > Definitions
> >
> > Hi, this is an automated email from Rob's (experimental) review bot. I found
> > a couple of common problems with your patch. Please see below.
>
> Do I need to send another patch? The mail says " Rob's (experimental) review bot".
"experimental" in the sense it may not work right. Such as they all
triggered spam filters. But I checked all these mails before they went
out, so the comments are correct.
> Previously for RZ/G1C upstreaming I have submitted the patches in similar fashion.
> Is anything changed?
Yes, I'm tired of manually providing these comments. If there's no
other comments though, then it is fine to apply as is.
Rob
prev parent reply other threads:[~2018-08-10 15:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-02 14:56 [PATCH v2 4/5] clk: renesas: Add r8a774a1 CPG Core Clock Definitions Biju Das
2018-08-03 8:48 ` Geert Uytterhoeven
[not found] ` <5b6cc306.1c69fb81.25824.1225@mx.google.com>
2018-08-10 7:35 ` Biju Das
2018-08-10 15:40 ` Rob Herring [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='CAL_Jsq+ApABam=zc-peomPd-7hZ4zf0zvd=vPzdUmTXP80MXog@mail.gmail.com' \
--to=robh@kernel.org \
--cc=Chris.Paterson2@renesas.com \
--cc=biju.das@bp.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-renesas-soc@vger.kernel.org \
--cc=mark.rutland@arm.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).