From: Markus Elfring <Markus.Elfring@web.de>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-acpi@vger.kernel.org, linux-leds@vger.kernel.org,
linux-usb@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Jakob Riepler <jakob+lkml@paranoidlabs.org>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Rob Herring <robh@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Daniel Scally <djrscally@gmail.com>,
Danilo Krummrich <dakr@kernel.org>,
Jonathan Cameron <jic23@kernel.org>, Lee Jones <lee@kernel.org>,
Matti Vaittinen <mazziesaccount@gmail.com>,
Pavel Machek <pavel@kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>
Subject: Re: [PATCH 1/4] device property: Split fwnode_get_child_node_count()
Date: Tue, 11 Mar 2025 13:00:16 +0100 [thread overview]
Message-ID: <bf26ba74-ff44-4642-864e-2c54d49ead74@web.de> (raw)
In-Reply-To: <20250310150835.3139322-2-andriy.shevchenko@linux.intel.com>
> The new helper is introduced to allow counting the child firmware nodes
> of their parent without requiring a device to be passed. …
See also:
https://web.git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.14-rc6#n94
Regards,
Markus
next prev parent reply other threads:[~2025-03-11 12:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-10 14:54 [PATCH v1 0/4] leds: Introduce and use fwnode_get_child_node_count() Andy Shevchenko
2025-03-10 14:54 ` [PATCH v1 1/4] device property: Split fwnode_get_child_node_count() Andy Shevchenko
2025-03-11 9:51 ` Jonathan Cameron
2025-03-11 12:00 ` Markus Elfring [this message]
2025-03-11 12:05 ` [PATCH " Greg Kroah-Hartman
2025-03-12 11:36 ` [PATCH v1 " Heikki Krogerus
2025-03-14 13:43 ` Sakari Ailus
2025-03-14 20:12 ` Rafael J. Wysocki
2025-03-10 14:54 ` [PATCH v1 2/4] leds: pwm-multicolor: Use fwnode_get_child_node_count() Andy Shevchenko
2025-03-11 9:52 ` Jonathan Cameron
2025-03-10 14:54 ` [PATCH v1 3/4] leds: ncp5623: " Andy Shevchenko
2025-03-11 9:54 ` Jonathan Cameron
2025-03-12 10:57 ` Andy Shevchenko
2025-03-10 14:54 ` [PATCH v1 4/4] usb: typec: tcpm: " Andy Shevchenko
2025-03-11 9:55 ` Jonathan Cameron
2025-03-12 3:29 ` Kyle Tso
2025-03-12 11:36 ` Heikki Krogerus
2025-03-14 12:38 ` [PATCH v1 0/4] leds: Introduce and use fwnode_get_child_node_count() Lee Jones
2025-03-14 12:39 ` Lee Jones
2025-03-14 13:35 ` Andy Shevchenko
2025-03-21 11:03 ` Lee Jones
2025-04-10 9:13 ` Lee Jones
2025-04-10 9:12 ` Lee Jones
2025-04-15 16:57 ` [GIT PULL] Immutable branch between LEDS, Base and USB due for the v6.16 merge window Lee Jones
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=bf26ba74-ff44-4642-864e-2c54d49ead74@web.de \
--to=markus.elfring@web.de \
--cc=Jonathan.Cameron@huawei.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dakr@kernel.org \
--cc=djrscally@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=jakob+lkml@paranoidlabs.org \
--cc=jic23@kernel.org \
--cc=lee@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mazziesaccount@gmail.com \
--cc=pavel@kernel.org \
--cc=rafael@kernel.org \
--cc=robh@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