linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: santosh.shilimkar@oracle.com (santosh shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] keystone: psci: adds cpu_die implementation
Date: Thu, 25 Jun 2015 11:42:12 -0700	[thread overview]
Message-ID: <558C4B84.9030303@oracle.com> (raw)
In-Reply-To: <20150625172057.GA11952@leverpostej>

On 6/25/2015 10:20 AM, Mark Rutland wrote:
>>> I need rework and re-test the patch.
>>> One more question. Shall I post the dts related commit, which add PSCI
>>> command together with this commit? Or it may be posted later independently?
>>
>> The DTS and Kconfig changes can be seaprate patches, but they'll need to
>> go through at the same time.
>
> If your bootloader patches the DTB then you don't even need a dts
> update. That should make things less confusing for existing users...
>
More than confusing we need to keep existing DTB binding work with
updated kernel at least for as basic as booting all the CPUs.

Regards,
Santosh

  reply	other threads:[~2015-06-25 18:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-25 14:02 [PATCH] keystone: psci: adds cpu_die implementation Vitaly Andrianov
2015-06-25 14:45 ` Mark Rutland
2015-06-25 14:59   ` santosh shilimkar
2015-06-25 16:01     ` Vitaly Andrianov
2015-06-25 16:13       ` Mark Rutland
2015-06-25 16:55         ` Vitaly Andrianov
2015-06-25 16:57           ` Mark Rutland
2015-06-25 17:20             ` Mark Rutland
2015-06-25 18:42               ` santosh shilimkar [this message]
2015-06-26 16:57                 ` Vitaly Andrianov
2015-06-26 16:59                   ` Mark Rutland
2015-06-26 17:47                   ` Grygorii Strashko
2015-06-26 18:06                     ` Vitaly Andrianov
2015-06-26 18:41                     ` santosh shilimkar
2015-06-25 14:54 ` santosh shilimkar

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=558C4B84.9030303@oracle.com \
    --to=santosh.shilimkar@oracle.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 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).