From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] README.mx28: add
Date: Wed, 21 Mar 2012 20:27:40 +0100 [thread overview]
Message-ID: <201203212027.40860.marek.vasut@gmail.com> (raw)
In-Reply-To: <CAP9ODKo2xVZjq3+uH+CqP5eEHy8mTiXR0L7gqXKhEcVsUGrk=A@mail.gmail.com>
Dear Otavio Salvador,
> On Wed, Mar 21, 2012 at 16:21, Marek Vasut <marek.vasut@gmail.com> wrote:
> > This is copy-paste schizzle, can you please separate the CPU specific
> > parts into one file and put only the different parts into their
> > particular readmes?
>
> If you compare the v3 against the m28 one it is not a copy-paste
> anymore; it does has specific information and remove the
> not-applicable one. The v3 seems fine to me as is and makes easier to
> new users to find the desired information.
See my response, also next time please bother to Cc me, your chances of review
of the patch rise a lot by doing so ... thanks ;-)
Best regards,
Marek Vasut
prev parent reply other threads:[~2012-03-21 19:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-20 20:54 [U-Boot] [PATCH] README.mx28: add Otavio Salvador
2012-03-20 23:14 ` Fabio Estevam
2012-03-21 19:21 ` Marek Vasut
2012-03-21 19:24 ` Otavio Salvador
2012-03-21 19:27 ` Marek Vasut [this message]
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=201203212027.40860.marek.vasut@gmail.com \
--to=marek.vasut@gmail.com \
--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.