From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/7] mfd: ab8500-core: Apply the AB8500 CODEC's compatible string to its MFD cell
Date: Sun, 29 Jul 2012 21:28:07 +0100 [thread overview]
Message-ID: <20120729202806.GC4384@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20120727133633.GQ16859@sortiz-mobl>
On Fri, Jul 27, 2012 at 03:36:33PM +0200, Samuel Ortiz wrote:
> On Fri, Jul 27, 2012 at 01:38:51PM +0100, Lee Jones wrote:
> > Provide a compatible string for the AB8500 CODEC to aid in
> > configuration property look-up from its associated Device Tree
> > node.
> Applied as well.
I remain *deeply* unconvinced that this is tasteful design for the
device tree bindings, and it's certainly not needed urgently for v3.6 as
there's no DT bindings on the CODEC side.
next prev parent reply other threads:[~2012-07-29 20:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-27 12:38 [PATCH 0/7] Bugfixes and clean-ups bound for the v3.6 RCs Lee Jones
2012-07-27 12:38 ` [PATCH 1/7] ASoC: dapm: If one widget fails, do not force all subsequent widgets to fail too Lee Jones
2012-07-29 20:25 ` Mark Brown
2012-07-27 12:38 ` [PATCH 2/7] ASoC: ab8500: Inform SoC Core that we have our own I/O arrangements Lee Jones
2012-07-27 12:38 ` [PATCH 3/7] mfd: db8500-prcmu: Ensure AB8500 platform data is passed through MFD Core Lee Jones
2012-07-27 13:36 ` Samuel Ortiz
2012-07-27 12:38 ` [PATCH 4/7] mfd: ab8500-core: Apply the AB8500 CODEC's compatible string to its MFD cell Lee Jones
2012-07-27 13:36 ` Samuel Ortiz
2012-07-29 20:28 ` Mark Brown [this message]
2012-07-30 13:24 ` Samuel Ortiz
2012-09-14 16:05 ` Lee Jones
2012-09-19 11:28 ` Samuel Ortiz
2012-07-27 12:38 ` [PATCH 5/7] ARM: ux500: Remove unused snowball_of_platform_devs struct Lee Jones
2012-07-27 12:38 ` [PATCH 6/7] ARM: ux500: Fix merge error, so such struct 'snd_soc_u8500' Lee Jones
2012-07-27 12:38 ` [PATCH 7/7] ARM: ux500: Ensure probing of Audio devices when Device Tree is enabled Lee Jones
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=20120729202806.GC4384@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.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).