From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/5] ARM: mxs: Sort the mx23evk and mx23_olinuxino
Date: Mon, 2 Sep 2013 19:00:03 -0400 [thread overview]
Message-ID: <52251873.2000809@ti.com> (raw)
In-Reply-To: <CAP9ODKoaazeU1W0Eq2nwkafH2Yn1-vcNTDsGiSshBBrdZbk=Bw@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 08/31/2013 05:15 PM, Otavio Salvador wrote:
> On Sat, Aug 31, 2013 at 5:52 PM, Stefano Babic <sbabic@denx.de> wrote:
>> Am 31/08/2013 22:03, schrieb Marek Vasut:
>>
>>> I suppose there will be not much problem with this reorder ... it would be nice
>>> if you provided link for a patch or discussion.
>>>
>>
>> http://patchwork.ozlabs.org/patch/266253/
>>
>> Of course, each change in boards.cfg or MAINTAINER will generate a
>> conflict, as Otavio stated. I hope this patch will be merged soon.
>>
>> I propose we postpone this single patch until Albert's flow into
>> mainline - if we need then some clean up, we will do at that time.
>
> I am adding Albert and Tom in Cc.
>
> Anyone knows what is holding the MAINTAINER file rework from merge?
I like it, but given the current high conflict rate it has, I'm waiting
for Albert to decide he's ready to re-generate things, probably after he
gets back and re-syncs all the ARM trees.
- --
Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJSJRhzAAoJENk4IS6UOR1WVdEP/R4pr9E2sq90mIV6Qx1JIWw6
DIvXqa5tiQfEvkWXveiqOxZwEsAUIBeS7xsMKKQo5yyd3/kIQjoSZUbQt1QNLJVx
mDTXJIKfLEc43cbX5ywDhmmmNS7jB47cvrrAmOBN3L8EAn+GlpHYM0ZHKR9OLSRV
tP5WQ2zgpTKL3c5rNRqL073sxLFOoPaXJgh461OlESjcxm/FlJLvUpIYJtPZdKpB
ZJRbsqqeJbmFEKs4rf+//M4tVQwAtyqHPzLeAU1/fZ3Sx6s2A+aPeMOWuqYlpvik
o8CJ6H/1wkPmSYKZNpItu0jFJSonRq/bKMeC7izbPNODHbiZgLL4qbWqQ+v4Jo2w
l1S15brWNdIiUlLfvMLr4g1K0WObcBAaRwpL3EXd/sS7HSe4hCqTi5Se6bKKysEa
D0FLHRbcGEpsdbyqCi9DoCHEGViO+qon/nxpFWtxeNYSVcumHTVs0+Q/cx2W9qVV
WY6b8zkjnaj4QOgEIIDfRWcVQ3oQIFrSfPf8G/heAwqxyjEtg48baFpA9xk9wBRH
bvB32twE26yTmBKii4pT6Xhl2S1rJDVCPuHIpgHzsJmNT1uPla0gqkrIRHFWCJ2t
Rg+7IxfHvA8cee369M6dwvjsOvQN7oF0xenRaS7KrwgDdWAmzQ4umi+wbmU3CRzU
Jbqj3a7Wccsqqkm7pEdF
=KBB7
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-09-02 23:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-31 13:53 [U-Boot] [PATCH 1/5] ARM: mxs: Sort the mx23evk and mx23_olinuxino Marek Vasut
2013-08-31 13:53 ` [U-Boot] [PATCH 2/5] ARM: mxs: Document the power block initialization Marek Vasut
2013-09-10 17:17 ` Stefano Babic
2013-08-31 13:53 ` [U-Boot] [PATCH 3/5] ARM: mxs: Receive r0 and r1 passed from BootROM Marek Vasut
2013-09-10 17:18 ` Stefano Babic
2013-08-31 13:53 ` [U-Boot] [PATCH 4/5] ARM: mxs: Add Creative ZEN XFi3 board Marek Vasut
2013-09-10 17:21 ` Stefano Babic
2013-08-31 13:53 ` [U-Boot] [PATCH 5/5] ARM: mxs: Add SanDisk Sansa Fuze+ board Marek Vasut
2013-09-10 17:21 ` Stefano Babic
2013-08-31 18:48 ` [U-Boot] [PATCH 1/5] ARM: mxs: Sort the mx23evk and mx23_olinuxino Otavio Salvador
2013-08-31 18:51 ` Marek Vasut
2013-08-31 19:03 ` Otavio Salvador
2013-08-31 19:51 ` Marek Vasut
2013-08-31 19:55 ` Otavio Salvador
2013-08-31 20:03 ` Marek Vasut
2013-08-31 20:52 ` Stefano Babic
2013-08-31 21:14 ` Marek Vasut
2013-08-31 21:15 ` Otavio Salvador
2013-09-02 23:00 ` Tom Rini [this message]
2013-09-03 13:35 ` Otavio Salvador
2013-09-10 17:15 ` 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=52251873.2000809@ti.com \
--to=trini@ti.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.