public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Krzysztof Adamski <krzysztof.adamski@nokia.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Peter Collingbourne <pcc@google.com>,
	Guenter Roeck <linux@roeck-us.net>,
	Alexander Sverdlin <alexander.sverdlin@nokia.com>,
	Matija Glavinic-Pecotic <matija.glavinic-pecotic.ext@nokia.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] arm64: move efi_reboot to restart handler
Date: Fri, 28 Jan 2022 20:29:06 +0100	[thread overview]
Message-ID: <YfREAiRMjQ9ci4LC@shikoro> (raw)
In-Reply-To: <YfP0osb45uJldtM9@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 240 bytes --]


> +	/* We want this to take priority over PSCI which has priority of 129. */
> +	.priority = 130,

Is it an idea to add a #define for the PSCI priority somewhere and use
here the define + 1? Hardcoded priorities look a bit fragile to me.


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2022-01-28 19:29 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-28 13:50 [PATCH v2] arm64: move efi_reboot to restart handler Krzysztof Adamski
2022-01-28 14:21 ` Alexander Sverdlin
2022-01-28 15:14 ` Guenter Roeck
2022-01-28 16:01 ` Mark Rutland
2022-01-28 22:05   ` Krzysztof Adamski
2022-02-01 13:58     ` Mark Rutland
2022-02-02 12:40       ` Krzysztof Adamski
2022-02-02 14:01         ` Ard Biesheuvel
2022-02-02 16:47           ` Krzysztof Adamski
2022-02-02 17:52             ` Krzysztof Adamski
2022-02-15  8:44           ` Alexander Sverdlin
2022-02-15  8:44       ` Alexander Sverdlin
2022-02-15 14:30         ` Guenter Roeck
2022-02-15 15:01           ` Krzysztof Adamski
2022-02-15 16:57             ` Guenter Roeck
2022-02-15 17:03               ` Ard Biesheuvel
2022-02-16  9:11                 ` Krzysztof Adamski
2022-01-28 19:29 ` Wolfram Sang [this message]
2022-01-28 22:32   ` Krzysztof Adamski
2022-01-29  6:38     ` Wolfram Sang

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=YfREAiRMjQ9ci4LC@shikoro \
    --to=wsa+renesas@sang-engineering.com \
    --cc=alexander.sverdlin@nokia.com \
    --cc=catalin.marinas@arm.com \
    --cc=krzysztof.adamski@nokia.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=mark.rutland@arm.com \
    --cc=matija.glavinic-pecotic.ext@nokia.com \
    --cc=pcc@google.com \
    --cc=will@kernel.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