public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] ARM custodian change
Date: Wed, 19 Mar 2008 00:33:18 +0100	[thread overview]
Message-ID: <039901c88954$fecd1350$050514ac@atmel.com> (raw)
In-Reply-To: 200803182104.58917.sr@denx.de

> On Tuesday 18 March 2008, Ulf Samuelsson wrote:
>> > Here a short announcement about a change in the U-Boot ARM custodianship:
>> >
>> > Since the ARM platform is so broad and has multiple vendor
>> > specific "sub-architectures" it seemed necessary to add new U-Boot
>> > custodian branches for those architectures. Fortunately we had some
>> > volunteers. Here the list:
>> >
>> > u-boot-at91 (Atmel ARM)         Jean-Christophe Plagniol-Villard
>> > u-boot-pxa (XScale)             Jean-Christophe Plagniol-Villard
>> > u-boot-s3c24xx (Samsung ARM)    Harald Welte
>> >
>> > Again, thanks a lot to the (new) custodians. Your help is really
>> > appreciated.
>>
>> Would it not be better if the Atmel ARM was handled by the Atmel AT91
>> Product line
> 
> Could be, I really don't know. I don't remember seeing Atmel ARM patches 
> posted or reviewed by other Atmel than yourself.

They were sent in 3-4 years ago.
Since there were no response, they lost interest, and have not tried since then.
They are maintaining a separate U-Boot source package.

> 
> So for the time being, we gladly accept that Jean-Christophe volunteered to 
> take over this custodianship. From my point of view, he is doing a very good 
> job with his other U-Boot activities. So I expect that the AT91 support could 
> be handled better from now on.

Have no criticism against Jean-Christophe, but I think that support for 
new chips may be available earlier with the AT91 team.

> 
> But again, we are open for other suggestions here too. If you think someone at 
> Atmel is better suited to do this job, then please let us know.

I will not have the time to maintain, that is for sure.

I think that the issue needs to be raised with the AT91 team, but it might be that
the AT91 team decides that they rather work closely with Jean-Christophe.

Andrew Victor is doing a good job maintaining the AT91 Linux port
so there is a precedent for this already.

> 
> BTW: If somebody else feels suited to take over some open custodianships (PCI, 
> RTC, HWMON come to my mind right now), please let us know too. :)


> Thanks.
> 
> Best regards,
> Stefan


Best Regards
Ulf Samuelsson

  reply	other threads:[~2008-03-18 23:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-18  5:07 [U-Boot-Users] ARM custodian change Stefan Roese
2008-03-18 10:17 ` Wolfgang Denk
2008-03-18 14:55 ` Ulf Samuelsson
2008-03-18 20:04   ` Stefan Roese
2008-03-18 23:33     ` Ulf Samuelsson [this message]
2008-03-19  5:00       ` Stefan Roese
2008-03-19  7:41         ` Ulf Samuelsson
2008-03-20 17:36           ` Nicolas Ferre
2008-03-20 18:13             ` Stelian Pop
2008-03-21 10:38             ` Stefan Roese
2008-03-25 23:05               ` Ulf Samuelsson
2008-03-20 17:12       ` Nicolas Ferre
2008-03-26 10:14         ` Haavard Skinnemoen

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='039901c88954$fecd1350$050514ac@atmel.com' \
    --to=ulf.samuelsson@atmel.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