From: Srikar <ext-srikar.1.bhavanarayana@nokia.com>
To: ext Tony Lindgren <tony@atomide.com>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
jhnikula@gmail.com, linux@arm.linux.org.uk,
linux-omap@vger.kernel.org
Subject: Re: [PATCH 2/2] enabled vdda_dac regulator support tvout on rx51
Date: Wed, 22 Dec 2010 13:51:06 +0200 [thread overview]
Message-ID: <4D11E62A.4060701@nokia.com> (raw)
In-Reply-To: <20101130173954.GO17222@atomide.com>
Updated version of patch of this is available at
https://patchwork.kernel.org/patch/424731/
On 11/30/2010 07:39 PM, ext Tony Lindgren wrote:
> * Mark Brown <broonie@opensource.wolfsonmicro.com> [101129 10:27]:
>> On Mon, Nov 29, 2010 at 10:18:31AM -0800, Tony Lindgren wrote:
>>> * Mark Brown <broonie@opensource.wolfsonmicro.com> [101127 02:10]:
>>>> Yeah. Some of it will need to be __devinitdata for hotpluggable things
>>>> but most of it should be __initdata. I'll update the regulator API to
>>>> copy the constraints before the next merge window.
>>> OK sounds good to me.
>> FWIW the patch is "regulator: Copy constraints from regulators when
>> initialising them", posted for review today.
> Great, once that merges we'll start checking what can be __init or
> __init_or_module for the omap board-*.c files.
>
> Tony
next prev parent reply other threads:[~2010-12-22 11:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-25 15:52 [PATCH 1/2] Added video data to support tvout on rx51 Srikar
2010-11-25 15:52 ` [PATCH 2/2] enabled vdda_dac regulator " Srikar
2010-11-25 16:11 ` Mark Brown
2010-11-26 9:42 ` ext-srikar.1.bhavanarayana
2010-11-26 9:56 ` Srikar
2010-11-26 12:59 ` Mark Brown
2010-11-26 17:45 ` Tony Lindgren
2010-11-27 10:20 ` Mark Brown
2010-11-29 18:18 ` Tony Lindgren
2010-11-29 18:37 ` Mark Brown
2010-11-30 17:39 ` Tony Lindgren
2010-12-22 11:51 ` Srikar [this message]
2010-12-18 0:42 ` [PATCH 1/2] Added video data to " Tony Lindgren
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=4D11E62A.4060701@nokia.com \
--to=ext-srikar.1.bhavanarayana@nokia.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=jhnikula@gmail.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=tony@atomide.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