From: Nathan Lynch <nathanl@linux.ibm.com>
To: Laurent Dufour <ldufour@linux.ibm.com>
Cc: cheloha@linux.ibm.com, linuxppc-dev@lists.ozlabs.org,
Tyrel Datwyler <tyreld@linux.ibm.com>
Subject: Re: [PATCH] powerpc/pseries/mobility: ignore ibm,platform-facilities updates
Date: Tue, 19 Oct 2021 16:43:33 -0500 [thread overview]
Message-ID: <87wnm8y9kq.fsf@linux.ibm.com> (raw)
In-Reply-To: <6f72adc9-d28c-beeb-e21f-4a468d2bf0e3@linux.ibm.com>
Laurent Dufour <ldufour@linux.ibm.com> writes:
> Le 19/10/2021 à 00:37, Tyrel Datwyler a écrit :
>> On 10/18/21 9:34 AM, Nathan Lynch wrote:
>> The reality is that '/ibm,platform-facilities' and 'cache' nodes are the only
>> LPM scoped device tree nodes that allow node delete/add. So, as a one-off
>> workaround to deal with what I consider a bad firmware approach I think this is
>> probably the best approach barring getting firmware to move to an update
>> properties approach.
>
> I do agree, this is probably the best option until the firmware is moving to an
> update notification.
Just to be clear, my proposal is to carry this hack until *Linux* can
be changed to better support the current firmware behavior. There's
little point in trying to get firmware to change now.
next prev parent reply other threads:[~2021-10-19 21:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-18 16:34 [PATCH] powerpc/pseries/mobility: ignore ibm, platform-facilities updates Nathan Lynch
2021-10-18 22:37 ` Tyrel Datwyler
2021-10-18 23:16 ` Tyrel Datwyler
2021-10-19 9:05 ` Laurent Dufour
2021-10-19 21:43 ` Nathan Lynch [this message]
2021-10-19 21:36 ` [PATCH] powerpc/pseries/mobility: ignore ibm,platform-facilities updates Nathan Lynch
2021-10-19 23:02 ` [PATCH] powerpc/pseries/mobility: ignore ibm, platform-facilities updates Tyrel Datwyler
2021-10-20 15:54 ` [PATCH] powerpc/pseries/mobility: ignore ibm,platform-facilities updates Nathan Lynch
2021-10-20 17:34 ` [PATCH] powerpc/pseries/mobility: ignore ibm, platform-facilities updates Tyrel Datwyler
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=87wnm8y9kq.fsf@linux.ibm.com \
--to=nathanl@linux.ibm.com \
--cc=cheloha@linux.ibm.com \
--cc=ldufour@linux.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=tyreld@linux.ibm.com \
/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.