All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: sudeep.holla@arm.com (Sudeep Holla)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/3] arm64: kernel: rename __cpu_suspend to keep it aligned with arm
Date: Thu, 18 Jun 2015 16:08:45 +0100	[thread overview]
Message-ID: <5582DEFD.8070106@arm.com> (raw)
In-Reply-To: <20150618145505.GE31480@e104818-lin.cambridge.arm.com>



On 18/06/15 15:55, Catalin Marinas wrote:
> On Thu, Jun 18, 2015 at 03:41:32PM +0100, Sudeep Holla wrote:
>> This patch renames __cpu_suspend to cpu_suspend so that it's aligned
>> with ARM32. It also removes the redundant wrapper created.
>>
>> This is in preparation to implement generic PSCI system suspend using
>> the cpu_{suspend,resume} which now has the same interface on both ARM
>> and ARM64.
>>
>> Cc: Mark Rutland <mark.rutland@arm.com>
>> Reviewed-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
>> Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
>> ---
>>   arch/arm64/include/asm/cpuidle.h | 8 ++------
>>   arch/arm64/include/asm/suspend.h | 2 +-
>>   arch/arm64/kernel/cpuidle.c      | 4 ++--
>>   arch/arm64/kernel/psci.c         | 2 +-
>>   arch/arm64/kernel/suspend.c      | 6 +++---
>>   5 files changed, 9 insertions(+), 13 deletions(-)
>
> Acked-by: Catalin Marinas <catalin.marinas@arm.com>
>
> Does this patch depend on the other patches from Mark and Lorenzo or it
> can be merged earlier?
>

Though it's independent patch, I think it will conflict with Mark's
changes. But since all the ARM64 related changes in that series are
already in ARM64 for-next/core, it applies cleanly on it and I even gave
it a quick testing. So it can be merged earlier if you are fine with that.

Regards,
Sudeep

  reply	other threads:[~2015-06-18 15:08 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-16 13:50 [PATCH 0/2] PSCI: system suspend support Sudeep Holla
2015-06-16 13:50 ` [PATCH 1/2] arm64: kernel: rename __cpu_suspend to keep it aligned with arm Sudeep Holla
2015-06-17 13:57   ` Lorenzo Pieralisi
2015-06-16 13:50 ` [PATCH 2/2] drivers: firmware: psci: add system suspend support Sudeep Holla
2015-06-17 15:08   ` Lorenzo Pieralisi
2015-06-17 15:41     ` Sudeep Holla
2015-06-18 14:41 ` [PATCH v2 0/3] PSCI: " Sudeep Holla
2015-06-18 14:41   ` [PATCH v2 1/3] arm64: kernel: rename __cpu_suspend to keep it aligned with arm Sudeep Holla
2015-06-18 14:55     ` Catalin Marinas
2015-06-18 15:08       ` Sudeep Holla [this message]
2015-06-19 13:50         ` Catalin Marinas
2015-06-18 14:41   ` [PATCH v2 2/3] drivers: firmware: psci: define more generic PSCI_FN_NATIVE macro Sudeep Holla
2015-09-14 13:17     ` Lorenzo Pieralisi
2015-09-14 13:21       ` Sudeep Holla
2015-06-18 14:41   ` [PATCH v2 3/3] drivers: firmware: psci: add system suspend support Sudeep Holla
2015-07-14  6:17     ` Jisheng Zhang
2015-07-14  9:14       ` Sudeep Holla
2015-07-14  9:50         ` Jisheng Zhang
2015-07-14 11:02           ` Sudeep Holla
2015-07-14 11:40             ` Jisheng Zhang
2015-07-14 13:18               ` Sudeep Holla
2015-07-15  2:34                 ` Jisheng Zhang
2015-07-15 10:20                   ` Sudeep Holla
2015-09-14 13:23     ` Lorenzo Pieralisi
2015-09-14 13:32       ` Sudeep Holla
2015-06-18 18:13   ` [PATCH v2 0/3] PSCI: " Ashwin Chaugule

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=5582DEFD.8070106@arm.com \
    --to=sudeep.holla@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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 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.