devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ivan Khoronzhuk <ivan.khoronzhuk-l0cyMroinI0@public.gmane.org>
To: Santosh Shilimkar <santosh.shilimkar-l0cyMroinI0@public.gmane.org>
Cc: grygorii.strashko-l0cyMroinI0@public.gmane.org,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] ARM: dts: k2e-evm: add AEMIF/NAND device entry
Date: Fri, 9 May 2014 00:25:45 +0300	[thread overview]
Message-ID: <536BF659.5040706@ti.com> (raw)
In-Reply-To: <536BF55A.6030406-l0cyMroinI0@public.gmane.org>


On 05/09/2014 12:21 AM, Santosh Shilimkar wrote:
> On Thursday 08 May 2014 04:26 PM, Ivan Khoronzhuk wrote:
>> On 05/08/2014 10:17 PM, Santosh Shilimkar wrote:
>>> On Thursday 08 May 2014 02:59 PM, Ivan Khoronzhuk wrote:
>>>> Add AEMIF/NAND device entry.
>>>>
>>>> Signed-off-by: Ivan Khoronzhuk <ivan.khoronzhuk-l0cyMroinI0@public.gmane.org>
>>>> ---
>>>>    arch/arm/boot/dts/k2e-evm.dts | 52 +++++++++++++++++++++++++++++++++++++++++++
>>>>    1 file changed, 52 insertions(+)
>>>>
>>> Thanks. Will pick this up for 3.16
>>>
>> Ups. Seems I've not changed ubifs partition size, always think about 128 Mb, but here 512 Mb.
>> I will send updated version with correct partition size.
>>
>>
> I was about to reply that patch wasn't applying cleanly. V2 applied
> to for_3.16/dts branch.
>
> Can you also rebase the ke2 patch against the dts branch and
> repost it ?
>
> Thanks !!
>
> regards,
> Santosh

Sure

-- 
Regards,
Ivan Khoronzhuk

--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2014-05-08 21:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-08 18:59 [PATCH] ARM: dts: k2e-evm: add AEMIF/NAND device entry Ivan Khoronzhuk
     [not found] ` <1399575560-31090-1-git-send-email-ivan.khoronzhuk-l0cyMroinI0@public.gmane.org>
2014-05-08 19:17   ` Santosh Shilimkar
     [not found]     ` <536BD85E.8090505-l0cyMroinI0@public.gmane.org>
2014-05-08 20:26       ` Ivan Khoronzhuk
     [not found]         ` <536BE875.2070005-l0cyMroinI0@public.gmane.org>
2014-05-08 21:21           ` Santosh Shilimkar
     [not found]             ` <536BF55A.6030406-l0cyMroinI0@public.gmane.org>
2014-05-08 21:25               ` Ivan Khoronzhuk [this message]
2014-05-08 20:31   ` Ivan Khoronzhuk
     [not found]     ` <1399581089-2505-1-git-send-email-ivan.khoronzhuk-l0cyMroinI0@public.gmane.org>
2014-05-08 20:33       ` Ivan Khoronzhuk
2014-05-08 21:29       ` [PATCH v2] ARM: dts: k2l-evm: " Ivan Khoronzhuk
     [not found]         ` <1399584543-3256-1-git-send-email-ivan.khoronzhuk-l0cyMroinI0@public.gmane.org>
2014-05-08 21:34           ` Santosh Shilimkar
2014-05-08 20:32   ` [PATCH v2] ARM: dts: k2e-evm: " Ivan Khoronzhuk

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=536BF659.5040706@ti.com \
    --to=ivan.khoronzhuk-l0cymroini0@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=grygorii.strashko-l0cyMroinI0@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=santosh.shilimkar-l0cyMroinI0@public.gmane.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).