All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Pull request for u-boot-arm -> u-boot?
Date: Mon, 5 May 2014 20:53:11 +0200	[thread overview]
Message-ID: <201405052053.11241.marex@denx.de> (raw)
In-Reply-To: <CAP9ODKrsv3U-krvQ6RME4X8zipx2jx2R60s5CNtJuJmFRQYn_Q@mail.gmail.com>

On Monday, May 05, 2014 at 08:12:18 PM, Otavio Salvador wrote:
> On Mon, May 5, 2014 at 2:59 PM, Fabio Estevam <festevam@gmail.com> wrote:
> > On Mon, May 5, 2014 at 1:46 PM, Stephen Warren <swarren@wwwdotorg.org> 
wrote:
> >> Albert,
> >> 
> >> I was wondering when the next pull request for u-boot-arm/master ->
> >> u-boot/master was likely to be?
> >> 
> >> I asked because some changes to the Tegra USB driver went through the
> >> u-boot-tegra/master and hence are now in u-boot-arm/master, but not in
> >> u-boot-usb/master. I have some more USB driver changes which rely on the
> >> earlier USB patches, and these should really go through
> >> u-boot-usb/master rather than the Tegra/ARM tree. For this to happen,
> >> u-boot-usb/master needs to contain the patches currently in
> >> u-boot-arm/master, and the best way for that to happen is for those
> >> patches to get into u-boot/master so that u-boot-usb/master can merge
> >> them.
> >> 
> >> Or, should Marek just merge u-boot-arm/master into his tree directly?
> > 
> > Or should we have a 'u-boot-next' tree using the same concept as the
> > kernel 'linux-next'?
> 
> Please, u-boot-next!
> 
> It is clear we need this to scale the pull model.

As Stephen already explained, u-boot-next solves nothing. U-boot-next will 
actually be explicitly unhelpful here because I won't be able to work on top of 
it and then send PRs to Tom . This just cannot work as it would break history .

Best regards,
Marek Vasut

  reply	other threads:[~2014-05-05 18:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-05 16:46 [U-Boot] Pull request for u-boot-arm -> u-boot? Stephen Warren
2014-05-05 17:46 ` Marek Vasut
2014-05-09  8:39   ` Albert ARIBAUD
2014-05-05 17:46 ` Tom Rini
2014-05-09  9:57   ` Albert ARIBAUD
2014-05-05 17:59 ` Fabio Estevam
2014-05-05 18:12   ` Otavio Salvador
2014-05-05 18:53     ` Marek Vasut [this message]
2014-05-05 18:15   ` Stephen Warren
2014-05-05 18:40     ` Tom Rini
2014-05-05 18:52       ` Stephen Warren
2014-05-05 18:54       ` Marek Vasut

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=201405052053.11241.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 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.