From: Minkyu Kang <promsoft@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] SPEAr : Adding maintainer name for spear SoCs
Date: Fri, 5 Mar 2010 10:25:26 +0900 [thread overview]
Message-ID: <1f3430fb1003041725i2572d067sc54bccfd043f13cd@mail.gmail.com> (raw)
In-Reply-To: <20100304124417.61D1E28BBC@gemini.denx.de>
Dear Wolfgang and Tom,
On 4 March 2010 21:44, Wolfgang Denk <wd@denx.de> wrote:
> Dear Vipin KUMAR,
>
> In message <4B8F5122.60602@st.com> you wrote:
>> On 3/3/2010 8:26 PM, Tom wrote:
> ...
>> > Please move this up to be after
>> > Sangmoon Kim <dogoil@etinsys.com>
>> >
>> > ? ? debris ? ? ? ?MPC8245
>> > ? ? KVME080 ? ? ? ?MPC8245
>> >
>>
>> This is under Power PC systems section.
>> Do you really want me to move it into Power PC systems
>
> No, of course not.
>
>> Even in ARM systems, the ordering is not alphabetical.
>
> It should be. If you notice errors, then please submit a patch to fix
> this.
>
>> Is there any other logic followed for arranging maintainer names
>
> They are sorted within the respective architecture group
> alphabetically by the maintainer's last name.
If so, I should move smdkc100 up to be after Eric Millbrandt. right?
Thanks
Minkyu Kang
--
from. prom.
www.promsoft.net
next prev parent reply other threads:[~2010-03-05 1:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-02 5:16 [U-Boot] [PATCH 0/2] New mach ids and maintainer name added Vipin KUMAR
2010-03-02 5:16 ` [U-Boot] [PATCH 1/2] SPEAr : Adding maintainer name for spear SoCs Vipin KUMAR
2010-03-02 5:16 ` [U-Boot] [PATCH 2/2] SPEAr : Supporting new mach ids for spear310 and spear320 Vipin KUMAR
2010-03-05 14:06 ` Tom
2010-03-08 5:18 ` Vipin KUMAR
2010-03-03 14:56 ` [U-Boot] [PATCH 1/2] SPEAr : Adding maintainer name for spear SoCs Tom
2010-03-04 2:29 ` Minkyu Kang
2010-03-04 6:20 ` Vipin KUMAR
2010-03-04 12:44 ` Wolfgang Denk
2010-03-05 1:25 ` Minkyu Kang [this message]
2010-03-05 14:10 ` Tom
2010-03-08 5:16 Vipin KUMAR
2010-03-12 19:40 ` Tom
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=1f3430fb1003041725i2572d067sc54bccfd043f13cd@mail.gmail.com \
--to=promsoft@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.