From: Rob Herring <robh@kernel.org>
To: Ramesh Shanmugasundaram <ramesh.shanmugasundaram@bp.renesas.com>
Cc: mkl@pengutronix.de, wg@grandegger.com, pawel.moll@arm.com,
mark.rutland@arm.com, ijc+devicetree@hellion.org.uk,
galak@codeaurora.org, linux-renesas-soc@vger.kernel.org,
devicetree@vger.kernel.org, linux-can@vger.kernel.org,
netdev@vger.kernel.org, geert+renesas@glider.be,
horms+renesas@verge.net.au, chris.paterson2@renesas.com
Subject: Re: [PATCH] can: rcar_can: Add r8a7795 support
Date: Thu, 3 Mar 2016 16:22:57 -0600 [thread overview]
Message-ID: <20160303222257.GA5346@rob-hp-laptop> (raw)
In-Reply-To: <1456749445-50766-1-git-send-email-ramesh.shanmugasundaram@bp.renesas.com>
On Mon, Feb 29, 2016 at 12:37:25PM +0000, Ramesh Shanmugasundaram wrote:
> Added r8a7795 SoC support.
>
> Signed-off-by: Ramesh Shanmugasundaram <ramesh.shanmugasundaram@bp.renesas.com>
> ---
> Hi All,
>
> This patch is based on linux-can-next (tag:linux-can-next-for-4.6-20160226)
>
> Pinctrl & Clock related to the controller are already submitted as below:
>
> https://lkml.org/lkml/2016/2/25/546
> https://lkml.org/lkml/2016/2/26/452
> http://www.spinics.net/lists/arm-kernel/msg487238.html
>
> Changes since v1:
> * Rebased from linux-next to linux-can-next
> * Removed clock rounding hack (http://www.spinics.net/lists/netdev/msg366611.html)
> * CAN dtsi changes will be submitted separately based on linux-next (http://marc.info/?l=linux-can&m=145674764815430&w=2)
>
> Documentation/devicetree/bindings/net/can/rcar_can.txt | 11 +++++++++++
> drivers/net/can/Kconfig | 2 +-
> drivers/net/can/rcar_can.c | 1 +
> 3 files changed, 13 insertions(+), 1 deletion(-)
Acked-by: Rob Herring <robh@kernel.org>
prev parent reply other threads:[~2016-03-03 22:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 12:37 [PATCH] can: rcar_can: Add r8a7795 support Ramesh Shanmugasundaram
2016-03-03 22:22 ` 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=20160303222257.GA5346@rob-hp-laptop \
--to=robh@kernel.org \
--cc=chris.paterson2@renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=geert+renesas@glider.be \
--cc=horms+renesas@verge.net.au \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-can@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=pawel.moll@arm.com \
--cc=ramesh.shanmugasundaram@bp.renesas.com \
--cc=wg@grandegger.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