From: Stephen Warren <swarren@nvidia.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Tegra Patches
Date: Mon, 21 Nov 2011 17:12:11 -0700 [thread overview]
Message-ID: <4ECAE8DB.5070509@nvidia.com> (raw)
In-Reply-To: <CAPnjgZ2g0wwu4=ZfXGQ4Qu1jrG041qmzaK+SWyYvedsEWpsu+A@mail.gmail.com>
On 11/21/2011 05:05 PM, Simon Glass wrote:
> On Mon, Nov 21, 2011 at 3:30 PM, Stephen Warren <swarren@nvidia.com> wrote:
...
>> Is there a status update for the creation of a Tegra git that we could
>> fetch and branch from ?
>
> Well I could put up a tree, but it's a bit dangerous - the real place
> is patchwork.
I thought there was going to be a u-boot-tegra.git that a Tegra U-boot
maintainer would put the patches into once reviewed/approved, and then
send pull requests to Albert, like the other ARM SoCs? That's what I was
expecting to rebase on top of. Sure some patches will still be waiting
in patchwork, but the volume would presumably be a lot lower, and
there'd be fewer conflicts.
--
nvpublic
next prev parent reply other threads:[~2011-11-22 0:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-21 23:07 [U-Boot] Tegra Patches Simon Glass
2011-11-21 23:30 ` Stephen Warren
2011-11-22 0:05 ` Simon Glass
2011-11-22 0:12 ` Stephen Warren [this message]
2011-11-22 2:13 ` Simon Glass
2011-11-22 11:15 ` Wolfgang Denk
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=4ECAE8DB.5070509@nvidia.com \
--to=swarren@nvidia.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.