From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] u-boot-tegra/master and /next have been updated and uploaded to denx.de
Date: Fri, 12 Oct 2012 15:30:42 -0600 [thread overview]
Message-ID: <50788C02.1010308@wwwdotorg.org> (raw)
In-Reply-To: <CA+m5__JE00JVoJC-fenf7DeVTPzVDWHk-tYm3HeM768+4ypz8w@mail.gmail.com>
On 10/12/2012 03:26 PM, Tom Warren wrote:
> Folks,
>
> u-boot-tegra/next has been updated with new patches from Lucas, Marc, and
> Stephen, rebased against u-boot-arm, and pushed to denx.de.
u-boot-tegra/next right now is based on u-boot-arm/master, but includes
patches that are both:
a) Already in u-boot-arm/next (but *not* u-boot-arm/master since master
is for the current release and next is for the next release)
b) New.
I think you want to create (rebase) u-boot-tegra/next based on
u-boot-arm/next, and drop the following patches (they would rebase out
anyway if you just rebase onto u-boot-arm/next):
c699a7b tegra: nand: add board pinmux
c7560dd tegra: clean up board include hell
1ddfbf3 tegra: add funcmux entry for NAND attached to KBC
8d49ab8 tegra20: rework UART GPIO handling
5904a2e tegra20: add clock_set_pllout function
0e0eb51 tegra20: complete periph_id enum
7811a6d tegra: enable CONFIG_CMD_PART
517ef6d Tegra20: Move some include files to arch-tegra for sharing with
Tegra30
1367676 Tegra20: Move some code files to common directories for upcoming
Tegra30 patches.
7d92ef4 tegra: Rename Medcom to Medcom-Wide
c527d55 tegra: Update Avionic Design vendor prefix
next prev parent reply other threads:[~2012-10-12 21:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+m5__JCiMDwMD-2fgLY=YHvBLU9GwXQkg3n5Ku7NEyUi+zDGQ@mail.gmail.com>
[not found] ` <CA+m5__+QkDOG1L_QK+4iMUN386Cp4EoPLuzhsH7yKYMsEc9Rtg@mail.gmail.com>
[not found] ` <1346825573.1487.3.camel@tellur>
[not found] ` <50470864.6080903@compulab.co.il>
2012-10-12 21:26 ` [U-Boot] u-boot-tegra/master and /next have been updated and uploaded to denx.de Tom Warren
2012-10-12 21:30 ` Stephen Warren [this message]
2012-10-13 10:18 ` Albert ARIBAUD
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=50788C02.1010308@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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.