From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
alsa-devel@alsa-project.org, linux-next@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>, Liam Girdwood <lrg@ti.com>
Subject: Re: [alsa-devel] linux-next: Tree for Oct 12 (sound/soc/codecs/wm1250-ev1)
Date: Thu, 13 Oct 2011 11:24:28 +0100 [thread overview]
Message-ID: <20111013102427.GG1098@sirena.org.uk> (raw)
In-Reply-To: <4E9634C9.3020404@xenotime.net>
On Wed, Oct 12, 2011 at 05:46:01PM -0700, Randy Dunlap wrote:
> When no GPIO kconfig options are enabled:
> (not GPIOLIB, not GENERIC_GPIO):
As ever the consumer side GPIO API is supposed to stub itself out when
not in use.
next prev parent reply other threads:[~2011-10-13 10:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-12 6:54 linux-next: Tree for Oct 12 Stephen Rothwell
2011-10-12 15:26 ` Randy Dunlap
2011-10-12 22:26 ` Stephen Rothwell
2011-10-12 22:31 ` Sedat Dilek
2011-10-13 0:46 ` linux-next: Tree for Oct 12 (sound/soc/codecs/wm1250-ev1) Randy Dunlap
2011-10-13 10:24 ` Mark Brown [this message]
2011-10-13 18:28 ` [alsa-devel] " Randy Dunlap
2011-10-13 21:58 ` 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=20111013102427.GG1098@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lrg@ti.com \
--cc=rdunlap@xenotime.net \
--cc=sfr@canb.auug.org.au \
/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