From: Franklin S Cooper Jr <fcooper@ti.com>
To: Santosh Shilimkar <santosh.shilimkar@oracle.com>,
<wg@grandegger.com>, <mkl@pengutronix.de>, <robh+dt@kernel.org>,
<ssantosh@kernel.org>, <linux@armlinux.org.uk>,
<linux-can@vger.kernel.org>, <netdev@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 0/3] ARM: dts: keystone-k2g: Add DCAN instances to 66AK2G
Date: Mon, 7 Aug 2017 16:31:43 -0500 [thread overview]
Message-ID: <8930852b-6995-3d41-440e-86f440b313ad@ti.com> (raw)
In-Reply-To: <69995971-2fe7-87f4-a46a-8ef4f729ffc5@oracle.com>
Hi Santosh,
On 08/04/2017 12:07 PM, Santosh Shilimkar wrote:
> Hi Franklin,
>
> On 8/2/2017 1:18 PM, Franklin S Cooper Jr wrote:
>> Add D CAN nodes to 66AK2G based SoC dtsi.
>>
>> Franklin S Cooper Jr (2):
>> dt-bindings: net: c_can: Update binding for clock and power-domains
>> property
>> ARM: configs: keystone: Enable D_CAN driver
>>
>> Lokesh Vutla (1):
>> ARM: dts: k2g: Add DCAN nodes
>>
> Any DCAN driver dependency with these patchset ? If not, I can
> queue this up so do let me know.
There aren't any dependencies.
>
> Regards,
> Santosh
next prev parent reply other threads:[~2017-08-07 21:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-02 20:18 Franklin S Cooper Jr
2017-08-02 20:18 ` [PATCH 1/3] dt-bindings: net: c_can: Update binding for clock and power-domains property Franklin S Cooper Jr
2017-08-10 16:35 ` Rob Herring
2017-08-02 20:18 ` [PATCH 2/3] ARM: dts: k2g: Add DCAN nodes Franklin S Cooper Jr
2017-08-02 20:18 ` [PATCH 3/3] ARM: configs: keystone: Enable D_CAN driver Franklin S Cooper Jr
2017-08-04 17:07 ` [PATCH 0/3] ARM: dts: keystone-k2g: Add DCAN instances to 66AK2G Santosh Shilimkar
2017-08-07 21:31 ` Franklin S Cooper Jr [this message]
2017-08-10 16:51 ` santosh.shilimkar
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=8930852b-6995-3d41-440e-86f440b313ad@ti.com \
--to=fcooper@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=santosh.shilimkar@oracle.com \
--cc=ssantosh@kernel.org \
--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
all inboxes | Powered by JetHome®