All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabio Estevam <festevam@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] mx6qsabrelite: Remove mx6qsabrelite code in favor of nitrogen6x
Date: Wed, 24 Jul 2013 09:48:35 -0300	[thread overview]
Message-ID: <CAOMZO5ADOz4sijvWtmfaAsQhTivrwCxZZodVKZiniP5DkMpTaw@mail.gmail.com> (raw)
In-Reply-To: <51EFCC63.1050409@denx.de>

Hi Stefano,

On Wed, Jul 24, 2013 at 9:45 AM, Stefano Babic <sbabic@denx.de> wrote:
> Hi Fabio,
>
> On 15/07/2013 19:29, Fabio Estevam wrote:
>> mx6qsabrelite and nitrogen6q boards are hardware compatible, so let's avoid the
>> code duplication and only use the nitrogen6x source code to make board code
>> maintainance easier.
>>
>> Tested booting a mainline device tree kernel on a mx6qsabrelite board.
>>
>> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
>> ---
>
> I get several "corrupt patch" even if it was sent as usual with
> git-send-email. Checking in e-mail source, seevral spaces are replaced
> by =20. I do not know if they are the cause: even trying to fix them, I
> cannot simply apply the patch. It seems that the mail server did some evil..
>
> Could you be so kind to repush the patch ?

No problem, I will re-send it later this week.

Regards,

Fabio Estevam

      reply	other threads:[~2013-07-24 12:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-15 17:29 [U-Boot] [PATCH v2] mx6qsabrelite: Remove mx6qsabrelite code in favor of nitrogen6x Fabio Estevam
2013-07-15 17:53 ` Otavio Salvador
2013-07-16 17:12 ` Eric Nelson
2013-07-17  7:42 ` Albert ARIBAUD
2013-07-17  8:04   ` Stefano Babic
2013-07-17  9:10     ` Albert ARIBAUD
2013-07-17  9:20       ` Stefano Babic
2013-07-24 12:45 ` Stefano Babic
2013-07-24 12:48   ` Fabio Estevam [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=CAOMZO5ADOz4sijvWtmfaAsQhTivrwCxZZodVKZiniP5DkMpTaw@mail.gmail.com \
    --to=festevam@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.