All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benoit Cousson <b-cousson@ti.com>
To: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
Cc: Tony Lindgren <tony@atomide.com>,
	Russell King <linux@arm.linux.org.uk>,
	Enric Balletbo i Serra <eballetbo@gmail.com>,
	Ezequiel Garcia <ezequiel.garcia@free-electrons.com>,
	linux-omap@vger.kernel.org, devicetree-discuss@lists.ozlabs.org
Subject: Re: [PATCH v2 2/2] ARM: dts: omap3-igep0030: Add NAND flash support
Date: Mon, 27 May 2013 10:54:44 +0200	[thread overview]
Message-ID: <51A31F54.1020001@ti.com> (raw)
In-Reply-To: <51A31E56.4020101@collabora.co.uk>

On 05/27/2013 10:50 AM, Javier Martinez Canillas wrote:
> On 05/27/2013 10:40 AM, Benoit Cousson wrote:
>> Hi Javier,
>>
> 
> Hi Benoit,
> 
>> On 05/10/2013 09:40 PM, Javier Martinez Canillas wrote:
>>> The IGEP COM Module has an 512MB NAND flash memory.
>>>
>>> Add a device node for this NAND and its parition layout.
>>>
>>> Signed-off-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
>>> ---
>>>
>>> Changes since v1:
>>>  - I just realized that sent a wrong version of the patch, sorry for the noise
>>
>> And what about the first one? For igep0020?
>>
>> Thanks,
>> Benoit
>>
> 
> For the igep0020 the first one was already correct. I just sent the wrong one
> for the igep0030 and that's why I had to send a v2 for this patch. Sorry for the
> confusion.

OK, I've just applied the v1 igep0020 and v2 igep0030 after fixing the
changelog typo" "parition".

Patches are available here:
git://git.kernel.org/pub/scm/linux/kernel/git/bcousson/linux-omap-dt.git
for_3.11/dts

Regards,
Benoit




  reply	other threads:[~2013-05-27  8:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-10 19:40 [PATCH v2 2/2] ARM: dts: omap3-igep0030: Add NAND flash support Javier Martinez Canillas
2013-05-27  8:40 ` Benoit Cousson
2013-05-27  8:50   ` Javier Martinez Canillas
2013-05-27  8:54     ` Benoit Cousson [this message]
2013-05-27  9:08       ` Javier Martinez Canillas

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=51A31F54.1020001@ti.com \
    --to=b-cousson@ti.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=eballetbo@gmail.com \
    --cc=ezequiel.garcia@free-electrons.com \
    --cc=javier.martinez@collabora.co.uk \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=tony@atomide.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 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.