From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] mx28evk: Add a README file
Date: Tue, 27 Mar 2012 15:12:30 +0200 [thread overview]
Message-ID: <4F71BCBE.3030207@denx.de> (raw)
In-Reply-To: <CAOMZO5A6+AM_X7QvDN7V8ZYcoUAMJLCt=d40ZtuRFZEfhH44xQ@mail.gmail.com>
On 27/03/2012 14:30, Fabio Estevam wrote:
> Hi Stefano,
>
Hi Fabio,
> On 3/24/12, Marek Vasut <marex@denx.de> wrote:
>> Dear Fabio Estevam,
>>
>>> Add a README file for mx28evk board.
>>>
>>> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
>>
>> Acked-by: Marek Vasut <marex@denx.de>
>
> Would it be possible to have this patch applied for 2012.03? Or is it too late?
Thoretically, it is late. However, this is a documentation regarding a
feature we have since a lot of time. Before I see your mail, I was
merging the two patches...
>
> Since mx28evk will be introduced in 2012.03,
Exactly
> it would be nice to have
> its readme file.
I think the same. The two patches will be part of my next pull request
to Albert.
Best regards,
Stefano Babic
--
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de
=====================================================================
next prev parent reply other threads:[~2012-03-27 13:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-24 20:58 [U-Boot] [PATCH 1/2] mx28: Split the README into a common part and a m28 specific part Fabio Estevam
2012-03-24 20:58 ` [U-Boot] [PATCH 2/2] mx28evk: Add a README file Fabio Estevam
2012-03-24 22:15 ` Marek Vasut
2012-03-27 12:30 ` Fabio Estevam
2012-03-27 13:01 ` Marek Vasut
2012-03-27 13:29 ` Stefano Babic
2012-03-27 13:12 ` Stefano Babic [this message]
2012-03-28 9:50 ` Stefano Babic
2012-03-24 22:15 ` [U-Boot] [PATCH 1/2] mx28: Split the README into a common part and a m28 specific part Marek Vasut
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=4F71BCBE.3030207@denx.de \
--to=sbabic@denx.de \
--cc=u-boot@lists.denx.de \
/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.