From: "Shreyas B. Prabhu" <shreyas@linux.vnet.ibm.com>
To: mpe@ellerman.id.au
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
benh@kernel.crashing.org, paulus@samba.org,
mahesh@linux.vnet.ibm.com, maddy@linux.vnet.ibm.com,
"Shreyas B. Prabhu" <shreyas@linux.vnet.ibm.com>
Subject: [PATCH 0/3] powerpc/powernv: Cpuidle related cleanup
Date: Mon, 29 Feb 2016 17:52:57 +0530 [thread overview]
Message-ID: <1456748580-10519-1-git-send-email-shreyas@linux.vnet.ibm.com> (raw)
These patches are purely code movement and cleanup.
There is no functionality change.
Note, there are multiple style error reported for patch 1 and 2.
I think this is because checkpatch script mistakes the patches
as C code because of the presence of semi-colon in each line. I
for now have largely ignored these errors.
Shreyas B. Prabhu (3):
powerpc/powernv: Move CHECK_HMI_INTERRUPT to exception-64s header
powerpc/powernv: Encapsulate idle preparation steps in a macro
powerpc/powernv: make hypervisor state restore a function
arch/powerpc/include/asm/cpuidle.h | 68 ++++++++++++++
arch/powerpc/include/asm/exception-64s.h | 19 ++++
arch/powerpc/kernel/exceptions-64s.S | 29 +-----
arch/powerpc/kernel/idle_power7.S | 148 ++++++++-----------------------
4 files changed, 129 insertions(+), 135 deletions(-)
--
1.9.3
next reply other threads:[~2016-02-29 12:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 12:22 Shreyas B. Prabhu [this message]
2016-02-29 12:22 ` [PATCH 1/3] powerpc/powernv: Move CHECK_HMI_INTERRUPT to exception-64s header Shreyas B. Prabhu
2016-03-17 5:21 ` Paul Mackerras
2016-02-29 12:22 ` [PATCH 2/3] powerpc/powernv: Encapsulate idle preparation steps in a macro Shreyas B. Prabhu
2016-03-17 11:15 ` Paul Mackerras
2016-03-18 14:53 ` Shreyas B Prabhu
2016-03-19 0:21 ` Paul Mackerras
2016-03-21 13:27 ` Shreyas B Prabhu
2016-02-29 12:23 ` [PATCH 3/3] powerpc/powernv: Refactor hypervisor state restore code Shreyas B. Prabhu
2016-03-10 10:45 ` [PATCH 0/3] powerpc/powernv: Cpuidle related cleanup Shreyas B Prabhu
2016-03-11 1:00 ` Michael Ellerman
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=1456748580-10519-1-git-send-email-shreyas@linux.vnet.ibm.com \
--to=shreyas@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.vnet.ibm.com \
--cc=mahesh@linux.vnet.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
/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).