From: sudeep.holla@arm.com (Sudeep Holla)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] drivers: firmware: psci: unify enable-method binding on ARM {64, 32}-bit systems
Date: Tue, 26 Apr 2016 12:22:49 +0100 [thread overview]
Message-ID: <571F4F89.70006@arm.com> (raw)
In-Reply-To: <20160426190257.7b2e6a9a@xhacker>
Hi Jisheng,
On 26/04/16 12:02, Jisheng Zhang wrote:
> Dear Arnd, Sudeep,
>
> On Tue, 26 Apr 2016 12:49:00 +0200 Arnd Bergmann wrote:
>
[...]
>>
>> Applied to the fixes branch. I have to admit that I don't understand
>> how the compatible string is really used here, so I have to trust that
>> this cannot break any existing machine.
>
> To be honest, this breaks some Marvell DEBU's 32 bit SoCs' kernel, but these
Sorry for that, but it's better to fix it in the firmware/DT.
As I mentioned earlier it was never honored in the kernel before v4.6,
so technically nothing is broken yet :)
> SoCs' support are not mainlined yet, so it's fine to fix it as early as
> possible.
>
Good to hear that. Thanks indeed.
--
Regards,
Sudeep
prev parent reply other threads:[~2016-04-26 11:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-22 15:18 [PATCH v2] drivers: firmware: psci: unify enable-method binding on ARM {64, 32}-bit systems Sudeep Holla
2016-04-26 10:42 ` [PATCH v2] drivers: firmware: psci: unify enable-method binding on ARM {64,32}-bit systems Sudeep Holla
2016-04-26 10:49 ` [PATCH v2] drivers: firmware: psci: unify enable-method binding on ARM {64, 32}-bit systems Arnd Bergmann
2016-04-26 11:01 ` [PATCH v2] drivers: firmware: psci: unify enable-method binding on ARM {64,32}-bit systems Mark Rutland
2016-04-26 11:02 ` [PATCH v2] drivers: firmware: psci: unify enable-method binding on ARM {64, 32}-bit systems Arnd Bergmann
2016-04-26 11:02 ` [PATCH v2] drivers: firmware: psci: unify enable-method binding on ARM {64,32}-bit systems Sudeep Holla
2016-04-26 11:02 ` [PATCH v2] drivers: firmware: psci: unify enable-method binding on ARM {64, 32}-bit systems Jisheng Zhang
2016-04-26 11:22 ` Sudeep Holla [this message]
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=571F4F89.70006@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 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).