From: Mark Brown <broonie@sirena.org.uk>
To: pHilipp Zabel <philipp.zabel@gmail.com>
Cc: Liam Girdwood <lrg@slimlogic.co.uk>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/5] regulator: Pass regulator init data as explict argument when registering
Date: Mon, 19 Jan 2009 17:37:48 +0000 [thread overview]
Message-ID: <20090119173747.GE22473@sirena.org.uk> (raw)
In-Reply-To: <74d0deb30901190924q4bc4d1ffu5211a161af3f5e6e@mail.gmail.com>
On Mon, Jan 19, 2009 at 06:24:50PM +0100, pHilipp Zabel wrote:
> Good, I had a local patch that would pass bq24022_mach_info in
> regulator_init_data->driver_data instead of platform_data.
> Now that there is a possibility to pass platform_data, is there still
> need for the driver_data field in regulator_init_data and for the
> regulator_get_init_drvdata() function?
I'd not expect so, no. The driver doesn't get to see the constraints.
next prev parent reply other threads:[~2009-01-19 17:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-19 13:37 Mark Brown
2009-01-19 13:37 ` [PATCH 2/5] regulator: Allow init data to be supplied for bq24022 Mark Brown
2009-01-19 13:37 ` [PATCH 3/5] regulator: Allow init_data to be passed to fixed voltage regulators Mark Brown
2009-01-19 13:37 ` [PATCH 4/5] regulator: Make fixed voltage regulators visible in Kconfig Mark Brown
2009-01-19 13:37 ` [PATCH 5/5] regulator: Mark attributes table for virtual regulator static Mark Brown
2009-01-19 17:24 ` [PATCH 1/5] regulator: Pass regulator init data as explict argument when registering pHilipp Zabel
2009-01-19 17:37 ` Mark Brown [this message]
2009-01-20 20:10 ` Liam Girdwood
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=20090119173747.GE22473@sirena.org.uk \
--to=broonie@sirena.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=philipp.zabel@gmail.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
all inboxes | Powered by JetHome®