From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Ramesh Shanmugasundaram <ramesh.shanmugasundaram@bp.renesas.com>,
Simon Horman <horms@verge.net.au>,
Rob Herring <robh+dt@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
Chris Paterson <Chris.Paterson2@renesas.com>,
Magnus Damm <magnus.damm@gmail.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 0/2] Add R8A77970/Eagle CAN-FD support
Date: Fri, 27 Apr 2018 14:19:09 +0300 [thread overview]
Message-ID: <894de81f-024c-7b1c-7aca-bc7b3b193173@cogentembedded.com> (raw)
In-Reply-To: <TY2PR01MB19620E4689C0B881B540E4D4C38D0@TY2PR01MB1962.jpnprd01.prod.outlook.com>
Hello!
On 04/27/2018 12:46 PM, Ramesh Shanmugasundaram wrote:
> Thank you for your patch.
> Could you also update the dt bindings please? A separate patch or part of this series.
I'd posted it just before these patches, see:
https://patchwork.kernel.org/patch/10366727/
MBR, Sergei
next prev parent reply other threads:[~2018-04-27 11:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-26 20:26 [PATCH 0/2] Add R8A77970/Eagle CAN-FD support Sergei Shtylyov
2018-04-26 20:33 ` [PATCH 1/2] arm64: dts: renesas: r8a77970: add " Sergei Shtylyov
2018-04-27 12:35 ` Ramesh Shanmugasundaram
2018-05-02 9:26 ` Simon Horman
2018-04-26 20:34 ` [PATCH 2/2] arm64: dts: renesas: eagle: " Sergei Shtylyov
2018-04-27 12:35 ` Ramesh Shanmugasundaram
2018-05-02 9:33 ` Simon Horman
2018-04-27 9:46 ` [PATCH 0/2] Add R8A77970/Eagle " Ramesh Shanmugasundaram
2018-04-27 11:19 ` Sergei Shtylyov [this message]
2018-04-27 11:29 ` Ramesh Shanmugasundaram
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=894de81f-024c-7b1c-7aca-bc7b3b193173@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=Chris.Paterson2@renesas.com \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=horms@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=ramesh.shanmugasundaram@bp.renesas.com \
--cc=robh+dt@kernel.org \
--cc=will.deacon@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).