From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] arm64: psci: respect MIGRATE_INFO_TYPE
Date: Fri, 5 Sep 2014 13:39:52 +0100 [thread overview]
Message-ID: <20140905123951.GB20164@leverpostej> (raw)
In-Reply-To: <5409A571.8060502@cogentembedded.com>
[...]
> > + if (psci_ops.migrate_info_type &&
> > + psci_ops.migrate_info_type() != PSCI_0_2_TOS_MP) {
> > + pr_warn("Unable to handle UP trusted OS\n");
> > + return -EPERM;
>
> The above 2 lines are indented too much to the right.
Noted; locally fixed. Thanks.
The logic is the same regardless, so I won't send out a v2 unless
someone has an issue with that logic, rather than the style.
Mark.
next prev parent reply other threads:[~2014-09-05 12:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-05 11:22 [PATCH 0/2] PSCI: don't call CPU_OFF when it might fail Mark Rutland
2014-09-05 11:22 ` [PATCH 1/2] arm64: psci: respect MIGRATE_INFO_TYPE Mark Rutland
2014-09-05 11:58 ` Sergei Shtylyov
2014-09-05 12:39 ` Mark Rutland [this message]
2014-09-05 11:22 ` [PATCH 2/2] arm: psci: don't call CPU_OFF blindly Mark Rutland
2014-09-05 20:48 ` Stefano Stabellini
2014-09-08 10:22 ` Mark Rutland
2014-09-05 20:53 ` [PATCH 0/2] PSCI: don't call CPU_OFF when it might fail Stefano Stabellini
2014-09-08 10:24 ` Mark Rutland
2014-09-08 21:44 ` Stefano Stabellini
[not found] <1409915540-20044-1-git-send-email-mark.rutland@arm.com>
[not found] ` <1409915540-20044-2-git-send-email-mark.rutland@arm.com>
[not found] ` <CAJ5Y-eZqWsLT1ERWsdzCQASgzCfFTgn6fCBCpc7ceMoU2ONkNA@mail.gmail.com>
[not found] ` <20140905141345.GF20164@leverpostej>
2014-09-05 18:22 ` [PATCH 1/2] arm64: psci: respect MIGRATE_INFO_TYPE Ashwin Chaugule
2014-09-08 14:14 ` Mark Rutland
2014-09-08 14:25 ` Ashwin Chaugule
2014-09-08 14:50 ` Mark Rutland
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=20140905123951.GB20164@leverpostej \
--to=mark.rutland@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox