From: ccross@android.com (Colin Cross)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: Tegra: Seaboard board updates for audio
Date: Thu, 21 Jul 2011 11:48:11 -0700 [thread overview]
Message-ID: <CAMbhsRQuzO2EW33vFGcDM+=bKLkfEY6WLn_dr7Q7o7uOekA0gA@mail.gmail.com> (raw)
In-Reply-To: <74CDBE0F657A3D45AFBB94109FB122FF049EBDF13E@HQMAIL01.nvidia.com>
On Thu, Jul 21, 2011 at 8:37 AM, Stephen Warren <swarren@nvidia.com> wrote:
> Olof Johansson wrote at Wednesday, July 13, 2011 5:17 PM:
>> On Wed, Jul 13, 2011 at 2:57 PM, Stephen Warren <swarren@nvidia.com> wrote:
>> > * Initialize clock tree for audio
>> > * Add GPIO base definitions
>> > * Add audio GPIO definitions
>> > * Define platform data for WM8903 and ASoC machine driver
>> > * Add special case for Kaen to handle HP_MUTE GPIO
>> > * Register platform devices for audio
>> > * Update pinmux to cater for new GPIOs used for audio
>> >
>> > Signed-off-by: Stephen Warren <swarren@nvidia.com>
>>
>> Colin, sounds like you're collecting board patches this merge window, so:
>>
>> Acked-by: Olof Johansson <olof@lixom.net>
>
> Colin,
>
> Do you want me to ask Arnd to pick these patches up directly, or do you
> want to apply them to the Tegra for-next tree, and have Arnd pull them?
Normally I would want them to go through me so I have a chance to deal
with conflicts before it hits the arm-soc tree, but since Arnd has
already taken some patches for this release cycle, they might as well
go directly to him.
next prev parent reply other threads:[~2011-07-21 18:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-13 21:57 [PATCH 1/2] ARM: Tegra: Seaboard board updates for audio Stephen Warren
2011-07-13 21:57 ` [PATCH 2/2] ARM: Tegra: Seaboard: Add USB devices Stephen Warren
2011-07-13 23:17 ` Olof Johansson
2011-07-13 23:17 ` [PATCH 1/2] ARM: Tegra: Seaboard board updates for audio Olof Johansson
2011-07-21 15:37 ` Stephen Warren
2011-07-21 18:48 ` Colin Cross [this message]
2011-07-21 19:57 ` Stephen Warren
2011-07-21 20:07 ` Olof Johansson
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='CAMbhsRQuzO2EW33vFGcDM+=bKLkfEY6WLn_dr7Q7o7uOekA0gA@mail.gmail.com' \
--to=ccross@android.com \
--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;
as well as URLs for NNTP newsgroup(s).