From: Eric Nelson <eric.nelson@boundarydevices.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mx6qsabrelite: Remove mx6qsabrelite code in favor of nitrogen6x
Date: Mon, 15 Jul 2013 08:43:38 -0700 [thread overview]
Message-ID: <51E418AA.3070201@boundarydevices.com> (raw)
In-Reply-To: <CAOMZO5DVJxUBbuHn13oswV2FYjrBm4LWBsEa+TBq5od2nH_0wA@mail.gmail.com>
On 07/15/2013 08:33 AM, Fabio Estevam wrote:
> Hi Eric,
>
> On Mon, Jul 15, 2013 at 11:20 AM, Eric Nelson
> <eric.nelson@boundarydevices.com> wrote:
>
>> Thanks for pointing it out. I had missed this.
>>
>>
>>> rename board/{freescale/mx6qsabrelite/README =>
>>> boundary/nitrogen6x/README.mx6qsabrelite} (100%)
>>
>>
>> I also have to admit not having read this README.
>>
>> It appears to give pretty bad advice, suggesting that the
>> user use the iMX6DQ_SPI_to_uSDHC3.bin shim to force
>> boot from SDHC3.
>>
>> I think this explains how people keep ending up at that
>> stale Linaro post.
>
> As I explained to Otavio, this patch does not attempt to introduce any
> change in current behaviour.
>
> The only intention here is to get rid of code duplication.
>
> If we want to change the current behaviour and align it with
> nitrogen6x, then we should do this on a separate patch.
>
> I will address Stefano's suggestion of changing the MAINTAINER file
> and plan to send a v2 later today.
>
Ok.
next prev parent reply other threads:[~2013-07-15 15:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-15 2:40 [U-Boot] [PATCH] mx6qsabrelite: Remove mx6qsabrelite code in favor of nitrogen6x Fabio Estevam
2013-07-15 2:44 ` Otavio Salvador
2013-07-15 2:52 ` Fabio Estevam
2013-07-15 2:58 ` Otavio Salvador
2013-07-15 4:09 ` Eric Nelson
2013-07-15 4:23 ` Fabio Estevam
2013-07-15 14:20 ` Eric Nelson
2013-07-15 14:55 ` [U-Boot] Antwort: " Stephan Bauroth
2013-07-15 15:31 ` Eric Nelson
2013-07-15 15:33 ` [U-Boot] " Fabio Estevam
2013-07-15 15:43 ` Eric Nelson [this message]
2013-07-15 7:14 ` Stefano Babic
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=51E418AA.3070201@boundarydevices.com \
--to=eric.nelson@boundarydevices.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox