From: Thierry Reding <thierry.reding@avionic-design.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 4/7] tegra: Allow boards to perform early GPIO setup
Date: Mon, 4 Jun 2012 08:09:19 +0200 [thread overview]
Message-ID: <20120604060918.GA10718@avionic-0098.adnet.avionic-design.de> (raw)
In-Reply-To: <5FBF8E85CA34454794F0F7ECBA79798F379C41610A@HQMAIL04.nvidia.com>
* Tom Warren wrote:
> Thierry,
>
> > -----Original Message-----
> > From: Thierry Reding [mailto:thierry.reding at avionic-design.de]
> > Sent: Friday, May 25, 2012 11:00 AM
> > To: Stephen Warren
> > Cc: u-boot at lists.denx.de; Tom Warren; Simon Glass
> > Subject: Re: [PATCH v2 4/7] tegra: Allow boards to perform early GPIO setup
> >
> > * PGP Signed by an unknown key
> >
> > * Thierry Reding wrote:
> > > Furthermore I'll need to rebase the patches onto the Tegra branch due
> > > to the major restructuring of the configuration files.
> >
> > This isn't true. But I'll still have to respin because of the MAINTAINERS
> > entry and the other points that you brought up, so let me know if I should
> > add a patch for Seaboard.
> When you respin this, make sure to base it on current u-boot-tegra/master,
> and change any CONFIG_TEGRA2_MMC or _SPI references to CONFIG_TEGRA_MMC &
> _SPI (see my changes to rename tegra periph drivers for the upcoming Tegra3
> rearch).
I saw that you already carry a patch in your next branch that does the
renames in the tec.h configuration. Can I assume that when I respin with
those changes included in the patch that introduces TEC support you'll drop
that hunk from your patch? Or should I rather follow up with patches based on
your next branch?
Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20120604/bde83a5f/attachment.pgp>
next prev parent reply other threads:[~2012-06-04 6:09 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-25 13:46 [U-Boot] [PATCH v2 1/7] tegra: Rework Tamonten support Thierry Reding
2012-05-25 13:46 ` [U-Boot] [PATCH v2 2/7] tegra: medcom: Add device tree support Thierry Reding
2012-05-25 13:46 ` [U-Boot] [PATCH v2 3/7] tegra: plutux: " Thierry Reding
2012-05-25 13:46 ` [U-Boot] [PATCH v2 4/7] tegra: Allow boards to perform early GPIO setup Thierry Reding
2012-05-25 16:24 ` Stephen Warren
2012-05-25 17:31 ` Thierry Reding
2012-05-25 17:59 ` Thierry Reding
2012-05-31 20:35 ` Tom Warren
2012-06-04 6:09 ` Thierry Reding [this message]
2012-06-04 16:47 ` Tom Warren
2012-05-25 13:46 ` [U-Boot] [PATCH v2 5/7] tegra: Implement gpio_early_init() on Tamonten Thierry Reding
2012-05-25 16:27 ` Stephen Warren
2012-05-25 17:40 ` Thierry Reding
2012-05-25 18:56 ` Kai Poggensee
2012-05-29 14:57 ` Thierry Reding
2012-05-29 16:06 ` Stephen Warren
2012-05-25 13:46 ` [U-Boot] [PATCH v2 6/7] tegra: Use SD write-protect GPIO " Thierry Reding
2012-05-25 13:46 ` [U-Boot] [PATCH v2 7/7] tegra: Add Tamonten Evaluation Carrier support Thierry Reding
2012-05-25 16:31 ` Stephen Warren
2012-06-08 20:01 ` [U-Boot] [PATCH v2 1/7] tegra: Rework Tamonten support Allen Martin
2012-06-08 21:07 ` Stephen Warren
2012-06-08 21:27 ` Allen Martin
2012-06-09 5:28 ` Stephen Warren
2012-06-09 6:25 ` Allen Martin
2012-06-09 16:18 ` Stephen Warren
2012-06-11 9:29 ` Thierry Reding
2012-06-11 17:59 ` Allen Martin
2012-06-11 18:07 ` Thierry Reding
2012-06-11 18:03 ` Allen Martin
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=20120604060918.GA10718@avionic-0098.adnet.avionic-design.de \
--to=thierry.reding@avionic-design.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