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:29:37 +0200 [thread overview]
Message-ID: <4F71C0C1.8060501@denx.de> (raw)
In-Reply-To: <201203271501.13940.marex@denx.de>
On 27/03/2012 15:01, Marek Vasut wrote:
> Dear Fabio Estevam,
>
>> Hi Stefano,
>>
>> 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?
>
> You'd have to poke WD for that, though I personally think it would be
> beneficial.
Marek, I have not seen your e-mail - I had sent my answer to Wolfgang, too.
IMHO I consider the two patches as a fix (that is, a missing
documentation for a board is a bug...) and I have no problem to merge
them. If nobody complains, this is the way I will do.
Regards,
Stefano
--
=====================================================================
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:29 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 [this message]
2012-03-27 13:12 ` Stefano Babic
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=4F71C0C1.8060501@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.