From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] ARM custodian change
Date: Thu, 20 Mar 2008 17:12:36 +0000 (UTC) [thread overview]
Message-ID: <loom.20080320T165212-196@post.gmane.org> (raw)
In-Reply-To: 039901c88954$fecd1350$050514ac@atmel.com
Ulf Samuelsson <ulf.samuelsson <at> atmel.com> writes:
>
> > 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
[..]
> >> Would it not be better if the Atmel ARM was handled by the Atmel AT91
> >> Product line
We (the AT91 software team) do not have this opinion. It is very enriching
to work with people from the community.
> > 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.
Ulf, we do not lose interest ! We simply do not have the
opportunity to rebase and test our work against the latest developments
for all chips&boards.
This opportunity is here now and we will be glad to contribute.
> > 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.
We will, for sure, work with Jean-Christophe and all AT91 u-boot
contributors for new chips introduction.
> > 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.
It is exactly the kind of relationship we would like to build with the
new custodian.
Regards,
--
Nicolas Ferre
next prev parent reply other threads:[~2008-03-20 17:12 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
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 [this message]
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=loom.20080320T165212-196@post.gmane.org \
--to=nicolas.ferre@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