U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Custodian Repo for Broadcom (arm) boards
Date: Mon, 11 Apr 2016 18:08:34 -0400	[thread overview]
Message-ID: <20160411220834.GU13577@bill-the-cat> (raw)
In-Reply-To: <CAM7GXokK26-fcXyN9QsPc4aT-JGMrSvNOE9VKQ_q7CWFEzDOfg@mail.gmail.com>

On Mon, Apr 11, 2016 at 03:01:10PM -0700, Steve Rae wrote:
> Hi Tom,
> 
> On Mon, Apr 11, 2016 at 2:56 PM, Tom Rini <trini@konsulko.com> wrote:
> > On Mon, Apr 11, 2016 at 11:55:49AM -0700, Steve Rae wrote:
> >
> >> Tom & Albert,
> >> Please approve the creation of a custodian repo for the Broadcom (arm) boards.
> >> ( Wolfgang already has my public key... )
> >>
> >> Wolfgang stated:
> >> > Before I can set up a new custodian repo, please post your
> >> > offer on the U-Boot mailing list -  I think the chips in question
> >> > belong to the ARM architecture (?), so both the ARM custodian (Albert)
> >> > and Tom should agree with the creation of such a new repo.  Once I
> >> > have their "go" it is only a matter of minutes.
> >
> > So, I do have a few BCM patches outstanding (and I'm build testing them
> > now).  ELC kicked -rc1 out a week (I'll be tagging it once I have this
> > series happy enough to push out with it).  Are you expecting the volume
> > of boards to increase?  Thanks!
> 
> No -- only planning to add 2 new boards....
> It is just that with the current process, I waiting "months" to get
> patches applied - so Marek suggested that maybe I need to be a
> custodian, so that I can move things along....

Er, months?  Sorry, I'm not seeing it right away at least:
https://patchwork.ozlabs.org/project/uboot/list/?submitter=64015&state=*
(and questions about how did .... get into state ... ? are answered with
"I took a stab at it").

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20160411/0b233b43/attachment.sig>

  reply	other threads:[~2016-04-11 22:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-11 18:55 [U-Boot] Custodian Repo for Broadcom (arm) boards Steve Rae
2016-04-11 21:37 ` Stephen Warren
2016-04-11 21:40   ` Steve Rae
2016-04-11 21:56 ` Tom Rini
2016-04-11 22:01   ` Steve Rae
2016-04-11 22:08     ` Tom Rini [this message]
2016-04-11 22:13       ` Steve Rae
2016-04-11 22:34         ` Tom Rini
2016-04-11 22:54           ` Steve Rae
2016-04-12 12:55             ` 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=20160411220834.GU13577@bill-the-cat \
    --to=trini@konsulko.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