public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Custodians, Maintainers and old platforms
Date: Sun, 30 Sep 2012 07:19:04 +0200	[thread overview]
Message-ID: <201209300719.04483.marex@denx.de> (raw)
In-Reply-To: <20120930025041.GA15914@chokladfabriken.org>

Dear Stefan Kristiansson,

> On Fri, Sep 21, 2012 at 05:28:18PM -0700, Tom Rini 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.
> > 
> > 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.
> > 
> > And finally, if everyone really wants to go another direction with old
> > platforms, I'm open to discussion of course.  I just want to miminize
> > work done on platforms that aren't active and we don't know if they will
> > come back.
> 
> This made me realise that there are two old OpenRISC patches floating
> around that hasn't been applied to mainline.
> 
> http://patchwork.ozlabs.org/patch/142511/
> http://patchwork.ozlabs.org/patch/142510/
> 
> Apart from that I'm not experiencing any problems on this arch.

Tom, I think we should apply them please.

> It brings me to another question though,
> would it be possible to get a custodian tree for OpenRISC?

CCing Detlev.

> Stefan

Best regards,
Marek Vasut

  reply	other threads:[~2012-09-30  5:19 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
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 [this message]
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=201209300719.04483.marex@denx.de \
    --to=marex@denx.de \
    --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