All of lore.kernel.org
 help / color / mirror / Atom feed
From: ivan.khoronzhuk@ti.com (Ivan Khoronzhuk)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: k2e-evm: add AEMIF/NAND device entry
Date: Thu, 8 May 2014 23:26:29 +0300	[thread overview]
Message-ID: <536BE875.2070005@ti.com> (raw)
In-Reply-To: <536BD85E.8090505@ti.com>


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@ti.com>
>> ---
>>   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.


-- 
Regards,
Ivan Khoronzhuk

WARNING: multiple messages have this Message-ID (diff)
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: Thu, 8 May 2014 23:26:29 +0300	[thread overview]
Message-ID: <536BE875.2070005@ti.com> (raw)
In-Reply-To: <536BD85E.8090505-l0cyMroinI0@public.gmane.org>


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.


-- 
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

  reply	other threads:[~2014-05-08 20:26 UTC|newest]

Thread overview: 20+ 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
2014-05-08 18:59 ` Ivan Khoronzhuk
2014-05-08 19:17 ` Santosh Shilimkar
2014-05-08 19:17   ` Santosh Shilimkar
2014-05-08 20:26   ` Ivan Khoronzhuk [this message]
2014-05-08 20:26     ` Ivan Khoronzhuk
2014-05-08 21:21     ` Santosh Shilimkar
2014-05-08 21:21       ` Santosh Shilimkar
2014-05-08 21:25       ` Ivan Khoronzhuk
2014-05-08 21:25         ` Ivan Khoronzhuk
2014-05-08 20:31 ` Ivan Khoronzhuk
2014-05-08 20:31   ` Ivan Khoronzhuk
2014-05-08 20:33   ` Ivan Khoronzhuk
2014-05-08 20:33     ` Ivan Khoronzhuk
2014-05-08 21:29   ` [PATCH v2] ARM: dts: k2l-evm: " Ivan Khoronzhuk
2014-05-08 21:29     ` Ivan Khoronzhuk
2014-05-08 21:34     ` Santosh Shilimkar
2014-05-08 21:34       ` Santosh Shilimkar
2014-05-08 20:32 ` [PATCH v2] ARM: dts: k2e-evm: " Ivan Khoronzhuk
2014-05-08 20:32   ` 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=536BE875.2070005@ti.com \
    --to=ivan.khoronzhuk@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.