From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 4/5] Tegra board updates for 3.3
Date: Tue, 27 Dec 2011 23:09:11 +0000 [thread overview]
Message-ID: <201112272309.11498.arnd@arndb.de> (raw)
In-Reply-To: <CAOesGMh7P6-=LbgUbYe1o7iO_-yALjce3H9ujXHW8hhikeTOsQ@mail.gmail.com>
On Wednesday 21 December 2011, Olof Johansson wrote:
> Please pull the below board updates for tegra for the 3.3 merge window.
>
> Some of the board changes went into the soc branch due to close
> dependencies, most of these are pinmux cleanup and prep for pinctrl
> integration.
>
>
> They are based on the for-3.3/soc branch.
Ok, pulled into the next/boards branch.
> The following changes since commit 6cc04a4420391c3f034afe8ea6e28d75912a70a3:
>
> arm/tegra: Compile tegra_dt_init_irq only when CONFIG_OF (2011-12-19
> 18:07:22 -0800)
>
> are available in the git repository at:
> git://git.kernel.org/pub/scm/linux/kernel/git/olof/tegra.git for-3.3/boards
>
> Leon Romanovsky (1):
> ARM: tegra: paz00: Fix board pinmux table.
>
> Marc Dietrich (1):
> ARM: tegra: paz00: add support for wakeup gpio key
>
> Olof Johansson (1):
> arm/tegra: remove __initdata annotation from pinmux tables
>
> Stephen Warren (9):
> arm/tegra: Split Seaboard GPIO table to allow for Ventana
I only just noticed that you are inconsistent with the formatting of the
patch subjects. We had a discussion about this a few months back and decided
to standardize on "ARM: tegra:" instead of "arm/tegra".
Please move to that style in future patches.
Thanks,
Arnd
next prev parent reply other threads:[~2011-12-27 23:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-21 19:15 [GIT PULL 4/5] Tegra board updates for 3.3 Olof Johansson
2011-12-27 23:09 ` Arnd Bergmann [this message]
2011-12-27 23:23 ` Olof Johansson
2011-12-28 13:22 ` Shawn Guo
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=201112272309.11498.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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