From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Zijun Hu <zijun_hu@icloud.com>
Cc: Zijun Hu <quic_zijuhu@quicinc.com>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
"Rafael J. Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>, Daniel Scally <djrscally@gmail.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Danilo Krummrich <dakr@kernel.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: Re: [PATCH v2 1/1] device property: Add a note to the fwnode.h
Date: Tue, 8 Apr 2025 12:50:39 +0300 [thread overview]
Message-ID: <Z_Txb26PyxBPM5oU@smile.fi.intel.com> (raw)
In-Reply-To: <Z--yNPfIz7TqqC42@smile.fi.intel.com>
On Fri, Apr 04, 2025 at 01:19:32PM +0300, Andy Shevchenko wrote:
> On Fri, Apr 04, 2025 at 10:59:41AM +0800, Zijun Hu wrote:
> > On 2025/4/1 00:35, Andy Shevchenko wrote:
...
> > > + * The respective API headers should
> > > + * guarantee all the required data types and definitions without including
> > > + * this header directly into the driver.
> >
> > device property(include/linux/property.h)
> > ^
> > |
> > firmware node(include/linux/fwnode.h)
> > ^ ^ ^ ^
> > | | | |
> > DT ACPI SWNODE ...
> >
> > For various firmware implementations(DT|ACPI|SWNODE...), i feel we may
> > allow them include fwnode.h by their header or source files.
>
> That's the point, yes. And that's what exactly I put under the first sentence.
> The device property providers are not the leaf drivers in this sense.
FWIW, Rafael proposed better wording which I'm going to use in v3 in the header.
Commit message would be similar, though.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2025-04-08 9:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-31 16:35 [PATCH v2 1/1] device property: Add a note to the fwnode.h Andy Shevchenko
2025-04-03 10:03 ` Zijun Hu
2025-04-03 11:00 ` Andy Shevchenko
2025-04-04 2:59 ` Zijun Hu
2025-04-04 10:19 ` Andy Shevchenko
2025-04-08 9:50 ` Andy Shevchenko [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=Z_Txb26PyxBPM5oU@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=dakr@kernel.org \
--cc=djrscally@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=laurent.pinchart@ideasonboard.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=sakari.ailus@linux.intel.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