All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Custodians, Maintainers and old platforms
Date: Tue, 25 Sep 2012 09:02:06 -0700	[thread overview]
Message-ID: <5061D57E.5000005@ti.com> (raw)
In-Reply-To: <20120922032437.2b81f483@lilith>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 09/21/12 18:24, Albert ARIBAUD wrote:
> Hi Tom,
> 
> On Fri, 21 Sep 2012 17:28:18 -0700, Tom Rini <trini@ti.com> wrote:
> 
>> Hey all,
>> 
>> (I had attempted to bcc this to all listed maintainer, but that
>> upset Google greatly.  I'll send this out manually instead
>> later).
>> 
>> I'd like to put this out here for custodians and maintainers to 
>> consider, especially in light of the device model work that's not
>> just coming but has already started being posted.
>> 
>> One of the keys to the success of U-Boot has been the number of 
>> platforms that are supported.  But part of supporting platforms
>> is needing people to volunteer to maintain them long term and
>> help with testing changes and so forth.  So first of all, I've
>> just tagged v2012.10-rc1.  Please give this at least a basic test
>> on whatever platforms you're able to.
> 
> Just started some minimal testing on edmini (Marvell orion5x). Will
> be able to test on wireless_space (Marvell kirkwood). Might be able
> to test on TrimSlice (NVidia Tegra2). Sorry, no TI board handy. :)
> 
>> Second, with this, my next branch is now open and I'd like to
>> start it by asking that platforms that people wish to abandon be
>> removed.  With the device model, lots of code will need adjusting
>> and while it's mechanical in ways, it still needs to be run-time
>> tested.  And it's changes that someone must do.  I know others
>> have suggested adding or better publicizing our to-remove file.
>> But one of the advantages of git is that it's easy to bring
>> platforms back, should someone later wish to bring it back.  But
>> this also requires the removal to be done cleanly.
>> 
>> All of that said, I would like to stress that if you maintain a 
>> platform and you wish to help with the testing and perhaps even
>> the conversion effort, no matter the age of the platform it would
>> be welcome and appreciated.
> 
> As far as edmini and wireless_space are concerned, I am willing to
> give it a try. Where should I start?

Start by looking over the documents in doc/driver-model/ and talking
with Marek things seem odd.

- -- 
Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iQIcBAEBAgAGBQJQYdV+AAoJENk4IS6UOR1WxlsP+wfCswxWw5y8xhHrvb6Xhu/M
iqNYaHacLedTuT89GoxfvfLDmxYdSXbZ903s2dGALznYGASREZsJb40esz1IGvHq
FfTyAohHSTWQKBKjQLCyOVMOGJwH2OH9lodyh/Bxtyyq46jDEtSK1glPbrgcRoUu
zRF4vPc1iAQk0kszU5NU7X0HTJsgsIS6SuK20Pc3tKHrqxpYtOgxPAvwxlBQsGsR
d1wOJsRDmsVEjb2bv36FZIj1x5PCfw9jct39buyPrSZXSdbKgzEPgJ7f9dt07n6S
VKtjSoK82I2jSHU0Pf8XT81eEzM6qwEmMvtZV8uVQyJtsLZorQpOSLIhnAm7cA0q
ukrPU50zRdjHr+F7fz3BnbkQ1Ps9y2O+JuOW6Ljm0+vMKutD8Kju9vGAlK6xH2BB
R5MpmwnK10iR68JoxjNO4nWKHmUW5TQCA1E8+ACGEps78nnbG0TDQelAw/ZkM3IV
h4uhckszbo2dG0NjGZELYcMq4O8K5PlEjqdOWTS+4Ugb4T+eltoE3q3hMS0JNYWh
NGcqL0gxJ9U4NIZr2NhBR9qb7LGCF5zwSkUhjeY9ij2Dc6sgLK81WHsmFcc+fhox
tFJCA+x2qwe5TJLuuGsMc1VqxD+rVGnz6U3BJ/kd0xKrnyRpHfUg79mZ7M/7w/9C
AmekJdqMz3aUeS7mIjHO
=9PeZ
-----END PGP SIGNATURE-----

  reply	other threads:[~2012-09-25 16:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-22  0:28 [U-Boot] Custodians, Maintainers and old platforms Tom Rini
2012-09-22  1:24 ` Albert ARIBAUD
2012-09-25 16:02   ` Tom Rini [this message]
2012-09-28  4:12 ` R, Sricharan
2012-09-28 22:12   ` Marek Vasut
2012-09-30  7:18     ` R, Sricharan
2012-09-30 13:18       ` Marek Vasut
2012-10-01 14:16         ` R, Sricharan
2012-10-01 14:35           ` Marek Vasut
2012-09-30  2:50 ` Stefan Kristiansson
2012-09-30  5:19   ` Marek Vasut
2013-01-22 15:14     ` Detlev Zundel
2012-10-01 17:11   ` Tom Rini

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=5061D57E.5000005@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.