From: Qian Cai <quic_qiancai@quicinc.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Laurentiu Tudor <laurentiu.tudor@nxp.com>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH] software node: Skip duplicated software_node sysfs
Date: Wed, 17 Nov 2021 11:18:29 -0500 [thread overview]
Message-ID: <YZUrVdcI9nzTUJfn@quicinc.com> (raw)
In-Reply-To: <CAJZ5v0if7__bYSnNWYNd7c9MfG32Sm2_cRcw6Qr+C2t2ywE-tg@mail.gmail.com>
On Wed, Nov 17, 2021 at 03:45:34PM +0100, Rafael J. Wysocki wrote:
> > since we will no longer has a dev->fwnode pointer anymore. Do you
> > suggest to keep that pointer but convert the "secondary" to a linked
> > list instead?
>
> Yes, please.
Sounds good. I think that would simplify the changes of the existing
interfaces even though only to mantain one fwnode_head would be a bit
cleaner. Though, that cleanup could always be on top later if needed.
prev parent reply other threads:[~2021-11-17 16:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 20:03 [RFC PATCH] software node: Skip duplicated software_node sysfs Qian Cai
[not found] ` <CAHp75VcrWPdR8EVGpcsniQedT0J4X700N7thFs6+srTP1MTgwQ@mail.gmail.com>
2021-11-02 8:28 ` Heikki Krogerus
2021-11-02 8:32 ` Heikki Krogerus
2021-11-02 14:17 ` Qian Cai
2021-11-02 19:44 ` Qian Cai
2021-11-02 20:20 ` Andy Shevchenko
2021-11-02 20:26 ` Andy Shevchenko
2021-11-05 18:47 ` Qian Cai
2021-11-05 19:39 ` Andy Shevchenko
2021-11-08 16:07 ` Qian Cai
2021-11-08 18:06 ` Andy Shevchenko
2021-11-09 4:43 ` Qian Cai
2021-11-09 15:23 ` Qian Cai
2021-11-16 3:54 ` Qian Cai
2021-11-16 16:29 ` Rafael J. Wysocki
2021-11-17 14:38 ` Qian Cai
2021-11-17 14:45 ` Rafael J. Wysocki
2021-11-17 16:18 ` Qian Cai [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=YZUrVdcI9nzTUJfn@quicinc.com \
--to=quic_qiancai@quicinc.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=laurentiu.tudor@nxp.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).