From: Samuel Ortiz <sameo@linux.intel.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Margarita Olaya Cabrera <magi@slimlogic.co.uk>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mfd: Don't ask about the TPS65912 core driver in Kconfig
Date: Mon, 4 Jul 2011 16:21:01 +0200 [thread overview]
Message-ID: <20110704142101.GF3021@sortiz-mobl> (raw)
In-Reply-To: <1308750838-26534-1-git-send-email-broonie@opensource.wolfsonmicro.com>
Hi Mark,
On Wed, Jun 22, 2011 at 02:53:58PM +0100, Mark Brown wrote:
> The user has to select the I2C and SPI drivers individually and they select
> the core driver for the device so there's no point in presenting the user
> with an option for the core driver.
Thanks, patch applied.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
prev parent reply other threads:[~2011-07-04 14:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-22 13:53 [PATCH] mfd: Don't ask about the TPS65912 core driver in Kconfig Mark Brown
2011-06-23 17:14 ` Randy Dunlap
2011-07-04 14:21 ` Samuel Ortiz [this message]
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=20110704142101.GF3021@sortiz-mobl \
--to=sameo@linux.intel.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=magi@slimlogic.co.uk \
/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