From: Lee Jones <lee@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Brian Mak <makb@juniper.net>,
Herve Codina <herve.codina@bootlin.com>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2] mfd: core: Preserve OF node when ACPI handle is present
Date: Tue, 10 Mar 2026 09:21:48 +0000 [thread overview]
Message-ID: <20260310092148.GE183676@google.com> (raw)
In-Reply-To: <aarmKE49wgbIblRb@ashevche-desk.local>
On Fri, 06 Mar 2026, Andy Shevchenko wrote:
> On Fri, Mar 06, 2026 at 01:38:06PM +0000, Lee Jones wrote:
> > On Thu, 26 Feb 2026, Brian Mak wrote:
>
> ...
>
> > > + /*
> > > + * FIXME: The fwnode design doesn't allow proper stacking/sharing. This
> >
> > So when will this be fixed exactly?
>
> I don't know, it's a huge task that requires of redesigning how struct
> fwnode_handle looks like and how it cohabits with struct device. Do you
> you think that NOTE will be more appropriate, because it may span several
> releases.
If someone is going to do the work sometime in the near future, it can
stay as FIXME. A few releases isn't going to offend anyone. However,
if we're just going to sit on it and this is likely to be here for an
elongated period, it should be changed.
Any idea who is planning on working on it?
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2026-03-10 9:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 22:45 [PATCH v2] mfd: core: Preserve OF node when ACPI handle is present Brian Mak
2026-02-27 5:40 ` Andy Shevchenko
2026-03-06 13:38 ` Lee Jones
2026-03-06 14:35 ` Andy Shevchenko
2026-03-10 9:21 ` Lee Jones [this message]
2026-03-10 10:25 ` Andy Shevchenko
2026-03-11 17:00 ` Brian Mak
2026-03-11 17:20 ` Andy Shevchenko
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=20260310092148.GE183676@google.com \
--to=lee@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=herve.codina@bootlin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=makb@juniper.net \
--cc=stable@vger.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