From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: linux-kernel@vger.kernel.org,
Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: [PATCH 4/3] mfd: Correct regulator platform data
Date: Mon, 25 Jan 2010 19:33:50 +0000 [thread overview]
Message-ID: <1264448030-11447-1-git-send-email-broonie@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1264447598-11255-2-git-send-email-broonie@opensource.wolfsonmicro.com>
...and of course in my split of the driver into relevant per-tree
sections I managed to miss this update of the platform data for
the regulators.
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
---
Ideally it should be squashed down into patch 2.
include/linux/mfd/wm8994/pdata.h | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/include/linux/mfd/wm8994/pdata.h b/include/linux/mfd/wm8994/pdata.h
index 3e6a86a..96a5800 100644
--- a/include/linux/mfd/wm8994/pdata.h
+++ b/include/linux/mfd/wm8994/pdata.h
@@ -20,7 +20,7 @@
struct wm8994_ldo_pdata {
/** GPIOs to enable regulator, 0 or less if not available */
- int regulator_enables;
+ int enable;
const char *supply;
struct regulator_init_data *init_data;
--
1.6.6
next prev parent reply other threads:[~2010-01-25 19:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-25 19:25 [PATCH 0/3] WM8994 core driver Mark Brown
2010-01-25 19:26 ` [PATCH 1/3] mfd: Add WM8994 register definitions Mark Brown
2010-01-25 19:26 ` [PATCH 2/3] mfd: Add initial WM8994 support Mark Brown
2010-01-25 19:33 ` Mark Brown [this message]
2010-01-25 19:26 ` [PATCH 3/3] gpiolib: Add WM8994 GPIO support Mark Brown
2010-01-29 18:15 ` [PATCH 0/3] WM8994 core driver Mark Brown
2010-01-29 20:02 ` Samuel Ortiz
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=1264448030-11447-1-git-send-email-broonie@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sameo@linux.intel.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
Powered by JetHome