linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: fcooper@ti.com (Franklin S Cooper Jr)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] ARM: dts: keystone: Add support for new K2G evm
Date: Tue, 4 Apr 2017 13:42:05 -0500	[thread overview]
Message-ID: <ad424a8e-353d-c942-2e14-bd98b537d72d@ti.com> (raw)
In-Reply-To: <b3f2604f-2649-6319-3689-fbd84fa926bb@oracle.com>



On 04/04/2017 10:33 AM, Santosh Shilimkar wrote:
> On 4/3/2017 9:44 AM, santosh.shilimkar at oracle.com wrote:
>> Hi Franklin,
>>
>> On 3/30/17 8:29 AM, Franklin S Cooper Jr wrote:
>>> This patchset adds support for new K2G Industrial Communication Engine
>>> evm. For now only a bare minimal dts which will allow ram boot.
>>> Additional
>>> peripherals will be added when base K2G SoC patches are upstreamed
>>> allowing
>>> peripherals to be enabled.
>>>
>>
>>>   ARM: keystone: Create new binding for K2G ICE evm
>>>   ARM: dts: keystone: Add minimum support for K2G ICE evm
>>>
>> Can you clarify Rob's comment on second patch and re-post the updated
>> patch with his ack if you agree ? Will apply the series.
>>
> Just to be clear, you need to send v2 with Rob's comment addressed
> for me to pick it up.

Will do.
> 
> Regards,
> Snatosh

      reply	other threads:[~2017-04-04 18:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-30 15:29 [PATCH 0/2] ARM: dts: keystone: Add support for new K2G evm Franklin S Cooper Jr
2017-03-30 15:29 ` [PATCH 1/2] ARM: keystone: Create new binding for K2G ICE evm Franklin S Cooper Jr
2017-04-03 16:25   ` Rob Herring
2017-03-30 15:29 ` [PATCH 2/2] ARM: dts: keystone: Add minimum support " Franklin S Cooper Jr
2017-04-03 16:27   ` Rob Herring
2017-04-04 20:04     ` Franklin S Cooper Jr
2017-04-03 16:44 ` [PATCH 0/2] ARM: dts: keystone: Add support for new K2G evm santosh.shilimkar at oracle.com
2017-04-04 15:33   ` Santosh Shilimkar
2017-04-04 18:42     ` Franklin S Cooper Jr [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=ad424a8e-353d-c942-2e14-bd98b537d72d@ti.com \
    --to=fcooper@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).