From: "Rob Herring (Arm)" <robh@kernel.org>
To: Zijun Hu <zijun_hu@icloud.com>
Cc: devicetree@vger.kernel.org,
Saravana Kannan <saravanak@google.com>,
Zijun Hu <quic_zijuhu@quicinc.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/5] of: Introduce and apply private is_pseudo_property()
Date: Tue, 25 Feb 2025 08:44:33 -0600 [thread overview]
Message-ID: <174049458073.2358434.7158444780792381835.robh@kernel.org> (raw)
In-Reply-To: <20250224-of_bugfix-v1-2-03640ae8c3a6@quicinc.com>
On Mon, 24 Feb 2025 22:27:58 +0800, Zijun Hu wrote:
> From: Zijun Hu <quic_zijuhu@quicinc.com>
>
> There are several places which check if a property name is one of
> 'name'|'phandle'|'linux,phandle'.
>
> Introduce and apply private is_pseudo_property() for the check.
>
> Signed-off-by: Zijun Hu <quic_zijuhu@quicinc.com>
> ---
> drivers/of/base.c | 4 +---
> drivers/of/of_private.h | 7 +++++++
> drivers/of/overlay.c | 4 +---
> drivers/of/resolver.c | 4 +---
> 4 files changed, 10 insertions(+), 9 deletions(-)
>
Applied, thanks!
next prev parent reply other threads:[~2025-02-25 14:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 14:27 [PATCH 0/5] of: Trivial cleanup Zijun Hu
2025-02-24 14:27 ` [PATCH 1/5] of: Compare property names by of_prop_cmp() in of_alias_scan() Zijun Hu
2025-02-25 14:42 ` Rob Herring (Arm)
2025-02-24 14:27 ` [PATCH 2/5] of: Introduce and apply private is_pseudo_property() Zijun Hu
2025-02-25 14:44 ` Rob Herring (Arm) [this message]
2025-02-24 14:27 ` [PATCH 3/5] of: Correct property name comparison in __of_add_property() Zijun Hu
2025-02-25 14:38 ` Rob Herring
2025-02-25 15:04 ` Zijun Hu
2025-02-25 19:57 ` Rob Herring
2025-02-24 14:28 ` [PATCH 4/5] of: Do not change property state under __of_add_property() failure Zijun Hu
2025-02-25 14:41 ` Rob Herring
2025-02-25 15:24 ` Zijun Hu
2025-02-25 15:25 ` Zijun Hu
2025-02-24 14:28 ` [PATCH 5/5] of/platform: Do not use of_get_property() to test property presence Zijun Hu
2025-02-25 14:44 ` Rob Herring (Arm)
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=174049458073.2358434.7158444780792381835.robh@kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_zijuhu@quicinc.com \
--cc=saravanak@google.com \
--cc=zijun_hu@icloud.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®