From: Kevin Hilman <khilman@linaro.org>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap <linux-omap@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: [GIT PULL] OMAP: PM: voltagedomain cleanup for v3.11
Date: Mon, 17 Jun 2013 11:14:06 -0700 [thread overview]
Message-ID: <87r4g08v0x.fsf@linaro.org> (raw)
The following changes since commit 7d132055814ef17a6c7b69f342244c410a5e000f:
Linux 3.10-rc6 (2013-06-15 11:51:07 -1000)
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/voltdm
for you to fetch changes up to 63b0420c85096d4bb1a3ba365dbf6b970a58b8f7:
ARM: AM33xx: Remove the unused voltagedomain data (2013-06-17 07:26:44 -0700)
----------------------------------------------------------------
OMAP: PM: remove requirement for voltage domain data; remove dummy data
----------------------------------------------------------------
Rajendra Nayak (2):
ARM: OMAP2+: Powerdomain: Remove the need to always have a voltdm associated to a pwrdm
ARM: AM33xx: Remove the unused voltagedomain data
arch/arm/mach-omap2/Makefile | 1 -
arch/arm/mach-omap2/io.c | 1 -
arch/arm/mach-omap2/powerdomain.c | 5 ++++
arch/arm/mach-omap2/powerdomain.h | 2 ++
arch/arm/mach-omap2/prm33xx.c | 7 +++++
arch/arm/mach-omap2/voltage.h | 1 -
arch/arm/mach-omap2/voltagedomains33xx_data.c | 43 ---------------------------
7 files changed, 14 insertions(+), 46 deletions(-)
delete mode 100644 arch/arm/mach-omap2/voltagedomains33xx_data.c
WARNING: multiple messages have this Message-ID (diff)
From: khilman@linaro.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] OMAP: PM: voltagedomain cleanup for v3.11
Date: Mon, 17 Jun 2013 11:14:06 -0700 [thread overview]
Message-ID: <87r4g08v0x.fsf@linaro.org> (raw)
The following changes since commit 7d132055814ef17a6c7b69f342244c410a5e000f:
Linux 3.10-rc6 (2013-06-15 11:51:07 -1000)
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/voltdm
for you to fetch changes up to 63b0420c85096d4bb1a3ba365dbf6b970a58b8f7:
ARM: AM33xx: Remove the unused voltagedomain data (2013-06-17 07:26:44 -0700)
----------------------------------------------------------------
OMAP: PM: remove requirement for voltage domain data; remove dummy data
----------------------------------------------------------------
Rajendra Nayak (2):
ARM: OMAP2+: Powerdomain: Remove the need to always have a voltdm associated to a pwrdm
ARM: AM33xx: Remove the unused voltagedomain data
arch/arm/mach-omap2/Makefile | 1 -
arch/arm/mach-omap2/io.c | 1 -
arch/arm/mach-omap2/powerdomain.c | 5 ++++
arch/arm/mach-omap2/powerdomain.h | 2 ++
arch/arm/mach-omap2/prm33xx.c | 7 +++++
arch/arm/mach-omap2/voltage.h | 1 -
arch/arm/mach-omap2/voltagedomains33xx_data.c | 43 ---------------------------
7 files changed, 14 insertions(+), 46 deletions(-)
delete mode 100644 arch/arm/mach-omap2/voltagedomains33xx_data.c
next reply other threads:[~2013-06-17 18:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-17 18:14 Kevin Hilman [this message]
2013-06-17 18:14 ` [GIT PULL] OMAP: PM: voltagedomain cleanup for v3.11 Kevin Hilman
2013-06-18 8:12 ` Tony Lindgren
2013-06-18 8:12 ` 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=87r4g08v0x.fsf@linaro.org \
--to=khilman@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--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.