From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Shilimkar, Santosh" <santosh.shilimkar@ti.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"sameo@linux.intel.com" <sameo@linux.intel.com>,
Peter Ujfalusi <peter.ujfalusi@nokia.com>,
"Lopez Cruz, Misael" <x0052729@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Krishnamoorthy, Balaji T" <balajitk@ti.com>
Subject: Re: [PATCHv3 1/7] OMAP4: PMIC: Add support for twl6030 codec
Date: Wed, 7 Oct 2009 10:37:17 +0100 [thread overview]
Message-ID: <20091007093717.GA3169@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <EAF47CD23C76F840A9E7FCE10091EFAB02BB056090@dbde02.ent.ti.com>
On Wed, Oct 07, 2009 at 11:56:38AM +0530, Shilimkar, Santosh wrote:
[I've reflowed your mail to fit into 80 columns]
> Since there is some sort of dependency on ASOC series with TWL_6030
> core series by Balaji, its better that these gets merged in correct
> order to avoid reworks.
There's no ordering problem with ASoC providing the TWL6030 core patches
add the TWL6030_CORE symbol as the last thing in the merge. None of the
ASoC drivers will be built until that symbol is defined so the absence
of the core shouldn't matter.
next prev parent reply other threads:[~2009-10-07 9:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 7:29 [PATCHv3 1/7] OMAP4: PMIC: Add support for twl6030 codec Lopez Cruz, Misael
2009-10-06 8:46 ` Peter Ujfalusi
2009-10-06 16:35 ` Mark Brown
2009-10-07 6:26 ` [alsa-devel] " Shilimkar, Santosh
2009-10-07 9:37 ` Mark Brown [this message]
2009-10-07 9:40 ` Shilimkar, Santosh
2009-10-06 16:53 ` Lopez Cruz, Misael
2009-10-07 7:32 ` Peter Ujfalusi
2009-10-07 5:20 ` [alsa-devel] " Krishnamoorthy, Balaji T
2009-10-07 7:41 ` Peter Ujfalusi
2009-10-08 1:30 ` Lopez Cruz, Misael
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=20091007093717.GA3169@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=balajitk@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=peter.ujfalusi@nokia.com \
--cc=sameo@linux.intel.com \
--cc=santosh.shilimkar@ti.com \
--cc=x0052729@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox