From: Kevin Hilman <khilman@linaro.org>
To: Tony Lindgren <tony@atomide.com>
Cc: Nishanth Menon <nm@ti.com>, Arnd Bergmann <arnd@arndb.de>,
Paul Walmsley <paul@pwsan.com>, Benoit Cousson <b-cousson@ti.com>,
Santosh Shilimkar <santosh.shilimkar@ti.com>,
linux-omap@vger.kernel.org
Subject: Re: [PATCH] ARM: OMAP5: voltagedomain data: remove temporary OMAP4 voltage data
Date: Wed, 26 Jun 2013 08:10:56 -0700 [thread overview]
Message-ID: <87bo6ssy9r.fsf@linaro.org> (raw)
In-Reply-To: <20130626073056.GS5523@atomide.com> (Tony Lindgren's message of "Wed, 26 Jun 2013 00:30:57 -0700")
Tony Lindgren <tony@atomide.com> writes:
> * Kevin Hilman <khilman@linaro.org> [130625 17:24]:
>> Nishanth Menon <nm@ti.com> writes:
>>
>> > commit 20d49e9ccfece526db755940721aa13e331936d4
>> > (ARM: OMAP5: voltagedomain data: Add OMAP5 voltage domain data)
>> >
>> > Introduced dummy volt data for OMAP5 with OMAP4460 voltage information.
>> >
>> > However with the fixes introduced in later patches
>> >
>> > commit cd8abed1da91a3250aa4b3857479613a2b446f84
>> > (ARM: OMAP2+: Powerdomain: Remove the need to always have a voltdm
>> > associated to a pwrdm)
>> >
>> > We are no longer restricted in that respect. Further, OPP voltage
>> > information is supposed to be provided by dts information. This needs
>> > to be added in future patches as various voltage modules are converted
>> > to dts.
>> >
>> > This also fixes the build breakage for voltagedomains54xx_data.c when just
>> > OMAP5 SoC is enabled: https://patchwork.kernel.org/patch/2764191/
>> >
>> > Reported-by: Arnd Bergmann <arnd@arndb.de>
>> > Signed-off-by: Nishanth Menon <nm@ti.com>
>> > Cc: Kevin Hilman <khilman@deeprootsystems.com>
>> > Cc: Benoit Cousson <b-cousson@ti.com>
>> > Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>
>> > Cc: Paul Walmsley <paul@pwsan.com>
>> > Cc: Tony Lindgren <tony@atomide.com>
>> > Cc: linux-omap@vger.kernel.org
>>
>> Acked-by: Kevin Hilman <khilman@linaro.org>
>>
>> Arnd, to make it easy, below is a pull request for this fix on top of
>> arm-soc/omap/omap5.
>
> This can get easily lost, might be best to send a new email with
> [GIT PULL] in the subject.
Done.
prev parent reply other threads:[~2013-06-26 15:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-25 23:56 [PATCH] ARM: OMAP5: voltagedomain data: remove temporary OMAP4 voltage data Nishanth Menon
2013-06-25 23:58 ` Santosh Shilimkar
2013-06-26 0:18 ` Kevin Hilman
2013-06-26 7:30 ` Tony Lindgren
2013-06-26 14:52 ` Arnd Bergmann
2013-06-26 15:10 ` Kevin Hilman [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=87bo6ssy9r.fsf@linaro.org \
--to=khilman@linaro.org \
--cc=arnd@arndb.de \
--cc=b-cousson@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=paul@pwsan.com \
--cc=santosh.shilimkar@ti.com \
--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;
as well as URLs for NNTP newsgroup(s).