From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Stephen Warren <swarren@nvidia.com>
Cc: "olof@lixom.net" <olof@lixom.net>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Leon Romanovsky <leon@leon.nu>, "lrg@ti.com" <lrg@ti.com>
Subject: Re: [PATCH 0/5] Add device tree support of audio (ALC5632) on PAZ00 board
Date: Tue, 31 Jan 2012 19:42:54 +0000 [thread overview]
Message-ID: <20120131194249.GF3429@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <74CDBE0F657A3D45AFBB94109FB122FF178E124441@HQMAIL01.nvidia.com>
[-- Attachment #1.1: Type: text/plain, Size: 454 bytes --]
On Tue, Jan 31, 2012 at 10:00:45AM -0800, Stephen Warren wrote:
> (Olof may wish to comment on whether he wishes the patches split up to
> apply the Tegra/ASoC parts separately, or merge them into both trees,
> to avoid any potential merge conflicts on the .dts files)
I'm leaving the last two patches to see what Olof thinks; Leon, if you
get to it first splitting the DTS file update from the patch updating
the machine driver would avoid any issue.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2012-01-31 19:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-31 7:25 [PATCH 0/5] Add device tree support of audio (ALC5632) on PAZ00 board Leon Romanovsky
[not found] ` <1327994757-26950-1-git-send-email-leon-2ukJVAZIZ/Y@public.gmane.org>
2012-01-31 18:00 ` Stephen Warren
2012-01-31 19:42 ` Mark Brown [this message]
[not found] ` <20120131194249.GF3429-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2012-02-01 6:45 ` Leon Romanovsky
2012-02-01 7:12 ` Olof Johansson
2012-01-31 19:33 ` Mark Brown
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=20120131194249.GF3429@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=leon@leon.nu \
--cc=linux-tegra@vger.kernel.org \
--cc=lrg@ti.com \
--cc=olof@lixom.net \
--cc=swarren@nvidia.com \
/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.