From: Johan Hovold <johan@kernel.org>
To: "Rafael J. Wysocki (Intel)" <rafael@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Danilo Krummrich <dakr@kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Daniel Scally <djrscally@gmail.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Bartosz Golaszewski <brgl@kernel.org>,
linux-acpi@vger.kernel.org, driver-core@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] software node: fix node group deregistration kernel-doc
Date: Fri, 20 Nov 2026 14:39:00 +0100 [thread overview]
Message-ID: <awBNdNq3bYlhu7DY@hovoldconsulting.com> (raw)
In-Reply-To: <CAJZ5v0jn32TL1N=PDY3v=9PL4ZJLainNUNN6ecXOJs=N0TSEjA@mail.gmail.com>
On Fri, Nov 20, 2026 at 02:18:24PM +0100, Rafael J. Wysocki wrote:
> On Mon, Nov 16, 2026 at 11:38 AM Johan Hovold <johan@kernel.org> wrote:
> >
> > Child software nodes hold a reference to their parent via kobj->parent
> > so there was never any need to deregister them in any particular order.
> >
> > Drop the misleading kernel-doc comments which suggest that deregistering
> > a parent node before a child could cause trouble.
> >
> > Note that parent nodes still need to be registered before their children
> > or registration will fail.
> >
> > Fixes: fc002f0f23e2 ("media: software_node: unregister software_nodes in reverse order")
> > Fixes: 0b8bf06f6719 ("device property: Sync descriptions of swnode array and group APIs")
> > Cc: Daniel Scally <djrscally@gmail.com>
> > Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > Signed-off-by: Johan Hovold <johan@kernel.org>
>
> LGTM
>
> Acked-by: Rafael J. Wysocki (Intel) <rafael@kernel.org>
Applied for -next.
Johan
prev parent reply other threads:[~2026-11-20 13:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-16 10:38 Johan Hovold
2026-11-20 13:18 ` Rafael J. Wysocki (Intel)
2026-11-20 13:39 ` Johan Hovold [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=awBNdNq3bYlhu7DY@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=brgl@kernel.org \
--cc=dakr@kernel.org \
--cc=djrscally@gmail.com \
--cc=driver-core@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=sakari.ailus@linux.intel.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
all inboxes | Powered by JetHome®