From: Kevin Hilman <khilman@linaro.org>
To: Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>
Cc: Tony Lindgren <tony@atomide.com>,
linux-omap <linux-omap@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Nishanth Menon <nm@ti.com>,
Santosh Shilimkar <santosh.shilimkar@ti.com>
Subject: [GIT PULL] OMAP5: fix voltage domains, remove wrong data
Date: Wed, 26 Jun 2013 08:10:45 -0700 [thread overview]
Message-ID: <87fvw4sya2.fsf@linaro.org> (raw)
Arnd,
Below is a pull request with a patch that fixes the build breakage you reported
related to voltage domains on OMAP5-only builds: https://patchwork.kernel.org/patch/2764191/
This applies on top of arm-soc/omap/omap5
Kevin
The following changes since commit 6503a8e109a639760408f874c1251060d563942e:
ARM: OMAP5: Remove unused include for ocp2scp (2013-06-09 21:17:15 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-omap-pm.git tags/omap-pm-v3.11/fixes/omap5-voltdm
for you to fetch changes up to 2ac524f151dbecb862c95b8f433267772caa800e:
ARM: OMAP5: voltagedomain data: remove temporary OMAP4 voltage data (2013-06-25 17:11:06 -0700)
----------------------------------------------------------------
OMAP5: PM: fix boot by removing unneeded dummy voltage domain data
----------------------------------------------------------------
Nishanth Menon (1):
ARM: OMAP5: voltagedomain data: remove temporary OMAP4 voltage data
arch/arm/mach-omap2/voltagedomains54xx_data.c | 10 ----------
1 file changed, 10 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: khilman@linaro.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] OMAP5: fix voltage domains, remove wrong data
Date: Wed, 26 Jun 2013 08:10:45 -0700 [thread overview]
Message-ID: <87fvw4sya2.fsf@linaro.org> (raw)
Arnd,
Below is a pull request with a patch that fixes the build breakage you reported
related to voltage domains on OMAP5-only builds: https://patchwork.kernel.org/patch/2764191/
This applies on top of arm-soc/omap/omap5
Kevin
The following changes since commit 6503a8e109a639760408f874c1251060d563942e:
ARM: OMAP5: Remove unused include for ocp2scp (2013-06-09 21:17:15 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-omap-pm.git tags/omap-pm-v3.11/fixes/omap5-voltdm
for you to fetch changes up to 2ac524f151dbecb862c95b8f433267772caa800e:
ARM: OMAP5: voltagedomain data: remove temporary OMAP4 voltage data (2013-06-25 17:11:06 -0700)
----------------------------------------------------------------
OMAP5: PM: fix boot by removing unneeded dummy voltage domain data
----------------------------------------------------------------
Nishanth Menon (1):
ARM: OMAP5: voltagedomain data: remove temporary OMAP4 voltage data
arch/arm/mach-omap2/voltagedomains54xx_data.c | 10 ----------
1 file changed, 10 deletions(-)
next reply other threads:[~2013-06-26 15:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-26 15:10 Kevin Hilman [this message]
2013-06-26 15:10 ` [GIT PULL] OMAP5: fix voltage domains, remove wrong data Kevin Hilman
2013-06-26 18:09 ` Arnd Bergmann
2013-06-26 18:09 ` Arnd Bergmann
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=87fvw4sya2.fsf@linaro.org \
--to=khilman@linaro.org \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=olof@lixom.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.