From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Saravana Kannan <saravanak@google.com>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
Daniel Scally <djrscally@gmail.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>,
Bartosz Golaszewski <brgl@bgdev.pl>
Subject: Re: [PATCH v1 1/1] device property: Clarify usage scope of some struct fwnode_handle members
Date: Mon, 4 Sep 2023 13:50:15 +0300 [thread overview]
Message-ID: <ZPW2Z7lRZTOhTU/m@kuha.fi.intel.com> (raw)
In-Reply-To: <20230904104046.1682875-1-andriy.shevchenko@linux.intel.com>
On Mon, Sep 04, 2023 at 01:40:46PM +0300, Andy Shevchenko wrote:
> Most of the struct fwnode_handle members are for exclusive use with
> device links framework. Clarify this by adding a respective comment.
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Yes, this is important clarification.
Reviewed-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> ---
> include/linux/fwnode.h | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/include/linux/fwnode.h b/include/linux/fwnode.h
> index 5700451b300f..2a72f55d26eb 100644
> --- a/include/linux/fwnode.h
> +++ b/include/linux/fwnode.h
> @@ -41,6 +41,8 @@ struct device;
> struct fwnode_handle {
> struct fwnode_handle *secondary;
> const struct fwnode_operations *ops;
> +
> + /* The below is used solely by device links, don't use otherwise */
> struct device *dev;
> struct list_head suppliers;
> struct list_head consumers;
> --
> 2.40.0.1.gaa8946217a0b
--
heikki
next prev parent reply other threads:[~2023-09-04 10:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 10:40 [PATCH v1 1/1] device property: Clarify usage scope of some struct fwnode_handle members Andy Shevchenko
2023-09-04 10:50 ` Heikki Krogerus [this message]
2023-09-04 11:02 ` Sakari Ailus
2023-09-18 16:59 ` Andy Shevchenko
2023-09-19 7:21 ` Greg Kroah-Hartman
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=ZPW2Z7lRZTOhTU/m@kuha.fi.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=brgl@bgdev.pl \
--cc=djrscally@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@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