From: Zijun Hu <zijun_hu@icloud.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Daniel Scally <djrscally@gmail.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Danilo Krummrich <dakr@kernel.org>, Rob Herring <robh@kernel.org>,
Saravana Kannan <saravanak@google.com>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, Zijun Hu <quic_zijuhu@quicinc.com>
Subject: Re: [PATCH v4 2/2] of: Align macro MAX_PHANDLE_ARGS with NR_FWNODE_REFERENCE_ARGS
Date: Wed, 26 Feb 2025 18:49:31 +0800 [thread overview]
Message-ID: <aa24e5cf-3a32-4792-be0f-9b8d190730d2@icloud.com> (raw)
In-Reply-To: <Z73RssDaLZ1NLpSZ@smile.fi.intel.com>
On 2025/2/25 22:20, Andy Shevchenko wrote:
> I would add here that the of.h includes fwnode.h already, so it doesn't
> add any new compile time dependency.
>
thank you Andy for comments.
include/linux/of.h:
struct device_node {
...
struct fwnode_handle fwnode; // this type is defined by fwnode.h
...
}
include/linux/fwnode.h:
struct fwnode_handle {...}
So of.h must include fwnode.h
Perhaps, of.h needs to include fwnode.h *explicitly* even if this is
another topic.
> Both patches LGTM,
> Acked-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
next prev parent reply other threads:[~2025-02-26 10:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-25 13:58 [PATCH v4 0/2] of: property: Fix potential firmware node reference's argument count got out of range Zijun Hu
2025-02-25 13:58 ` [PATCH v4 1/2] of: property: Increase NR_FWNODE_REFERENCE_ARGS Zijun Hu
2025-02-26 8:30 ` Sakari Ailus
2025-02-25 13:58 ` [PATCH v4 2/2] of: Align macro MAX_PHANDLE_ARGS with NR_FWNODE_REFERENCE_ARGS Zijun Hu
2025-02-25 14:20 ` Andy Shevchenko
2025-02-26 8:29 ` Sakari Ailus
2025-02-26 10:49 ` Zijun Hu [this message]
2025-02-26 8:30 ` Sakari Ailus
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=aa24e5cf-3a32-4792-be0f-9b8d190730d2@icloud.com \
--to=zijun_hu@icloud.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dakr@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=djrscally@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_zijuhu@quicinc.com \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=saravanak@google.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