[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8c51e02c-c262-4db8-b0fe-30462005f1c5@icloud.com>
Date: Tue, 25 Feb 2025 23:25:49 +0800
From: Zijun Hu <zijun_hu@...oud.com>
To: Rob Herring <robh@...nel.org>
Cc: Saravana Kannan <saravanak@...gle.com>, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, Zijun Hu <quic_zijuhu@...cinc.com>
Subject: Re: [PATCH 4/5] of: Do not change property state under
__of_add_property() failure
On 2025/2/25 22:41, Rob Herring wrote:
> On Mon, Feb 24, 2025 at 10:28:00PM +0800, Zijun Hu wrote:
>> From: Zijun Hu <quic_zijuhu@...cinc.com>
>>
>> Do not remove the property from list @np->deadprops if
>> __of_add_property() encounters -EEXIST failure.
> A property can never be on both np->deadprops and np->props.
i made this patch based on convention that
partial task which has been done successfully needs to be undid if fails
to do the remaining task.
It is okay to drop this patch based on condition you mentioned.
thank you. (^^)(^^)
Powered by blists - more mailing lists