From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] mx6qsabrelite: Remove mx6qsabrelite code in favor of nitrogen6x
Date: Wed, 17 Jul 2013 11:10:03 +0200 [thread overview]
Message-ID: <20130717111003.4357fb83@lilith> (raw)
In-Reply-To: <51E6500D.2090909@denx.de>
Hi Stefano,
On Wed, 17 Jul 2013 10:04:29 +0200, Stefano Babic <sbabic@denx.de>
wrote:
> Hi Albert,
>
> On 17/07/2013 09:42, Albert ARIBAUD wrote:
> > Hi Fabio,
> >
> > On Mon, 15 Jul 2013 14:29:28 -0300, Fabio Estevam
> > <fabio.estevam@freescale.com> 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>
> >> ---
> >
> > Hmm, why does this patch not show on Patchwork? Only its V1 does.
> >
>
> I am struggling for finding it, too. I have already seen a similar case
> in the past. Otavio remarked that when there is a rename, patchwork is
> not able to track it (bug in patchwork).
Since we have a clear example (and on the patchwork site where the
patchwork folks can dig as deep as they need), we could bring this up
to the patchwork list, with the M-IDs of the V1 and V2 patches.
I'd rather someone with a handle to the U-Boot mailing list do it, as
it may require digging there too.
Wolfgang?
> Stefano
Amicalement,
--
Albert.
next prev parent reply other threads:[~2013-07-17 9:10 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 [this message]
2013-07-17 9:20 ` Stefano Babic
2013-07-24 12:45 ` Stefano Babic
2013-07-24 12:48 ` Fabio Estevam
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=20130717111003.4357fb83@lilith \
--to=albert.u.boot@aribaud.net \
--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