Re: [PATCH v2 1/6] device property: document device_for_each_child_node macro

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Javier Carrasco <javier.carrasco.cruz@xxxxxxxxx>, linux-hwmon@xxxxxxxxxxxxxxx, linux-leds@xxxxxxxxxxxxxxx, linux-acpi@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxxxxxx, Andreas Kemnade <andreas@xxxxxxxxxxxx>, Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>, Daniel Scally <djrscally@xxxxxxxxx>, "David S. Miller" <davem@xxxxxxxxxxxxx>, Eric Dumazet <edumazet@xxxxxxxxxx>, Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>, Günter Röck <linux@xxxxxxxxxxxx>, Heikki Krogerus <heikki.krogerus@xxxxxxxxxxxxxxx>, Jakub Kicinski <kuba@xxxxxxxxxx>, Jean Delvare <jdelvare@xxxxxxxx>, Jonathan Cameron <jic23@xxxxxxxxxx>, Lee Jones <lee@xxxxxxxxxx>, Marcin Wojtas <marcin.s.wojtas@xxxxxxxxx>, Paolo Abeni <pabeni@xxxxxxxxxx>, Pavel Machek <pavel@xxxxxx>, "Rafael J. Wysocki" <rafael@xxxxxxxxxx>, Rob Herring <robh@xxxxxxxxxx>, Russell King <linux@xxxxxxxxxxxxxxx>, Sakari Ailus <sakari.ailus@xxxxxxxxxxxxxxx>
Subject: Re: [PATCH v2 1/6] device property: document device_for_each_child_node macro
From: Markus Elfring <Markus.Elfring@xxxxxx>
Date: Mon, 22 Jul 2024 09:15:26 +0200
Cc: LKML <linux-kernel@xxxxxxxxxxxxxxx>, Jonathan Cameron <Jonathan.Cameron@xxxxxxxxxx>
In-reply-to: <20240721-device_for_each_child_node-available-v2-1-f33748fd8b2d@gmail.com>
References: <20240721-device_for_each_child_node-available-v2-1-f33748fd8b2d@gmail.com>
Ui-outboundreport: notjunk:1;M01:P0:zMXmFfshu/w=;jAInkgB3vloWqW9kgqI8uWOuokM n5IXptcGeplXc/NaEZxVWLFa/Io9spgPH3TH2rzipw06aXs3s4jLjf8OdtwNUg3FjAhRA3Hql DwBz+TKODiNo8fLGqR6eT+RKe1fOWVw7n7M36LjzBOqI9yBTMPJTsaoz9nKAMZYO1YW2vPT1D Ijp7TUQbDQKs38m5li9TRE8vNg3/ncd/TRO+svPdwVNSK4sd8rH0o5JApRiCsMLQjt1pIwbqW YMXWDphWozW0ZAsch2EBNC2g6oyN2Jfmf40LjUEmste+oeuxLkDaLDfrgM1aw0Pq/oy0K9wEo 339RvtJ4EbCF0j7wXp+saUmj14wfnd4AILUNn4X50XyzhkMepw5BFqE5CFrCPMbRdatCnQWX0 8zNTWLMhx0GRNz6Dv6Ev5THZjS4SpmDN+XmfOFeridUqaF0PDe1Jzkf8fRrTj8SFHgoHMkuAr p1brIA/TFz8FsNK1FCQjrj/cTGlcX6CuNQln1AE4LbluuAul6BaLb7jpPnD1ywRFIPO/UO0rW TmW/SicScUoXAnQ6rj/S6t2RPfI0hJNmg8w8m0wZjwH/n+G/lYTATCSRXy8w8xcu4OtBV8rzs yiPg+aJpgaMs22MOv+XLlQuQ7Icot43zQ/MT/qp5WIpGDqZ8Xas+1b96QAjhINwkqRG10k8kV 76dR8pUGfLUk/+/tlXvDzLRtkoGkoWrpMk+14HDfMa8pzQ/TDNREQ3xcwSZkB78JSL9iygLRK wUQ0CGFNDAHufOB/UEJNuef3c7g5bD6IGNikxvOrEjXiA52fFGiyM5sHRpM8ys0dOL7nLU0YE egEY/c+H7mNDTsMF0eKES1PA==
User-agent: Mozilla Thunderbird

…
> + * Unavailable nodes are skipped i.e. this macro is implicitly _available_.
…

How good does presented information fit together in this comment line?

Regards,
Markus

Follow-Ups:
- Re: [PATCH v2 1/6] device property: document device_for_each_child_node macro
  - From: Greg Kroah-Hartman

References:
- [PATCH v2 1/6] device property: document device_for_each_child_node macro
  - From: Javier Carrasco

Prev by Date: Re: [PATCH v3 2/2] leds: Add LED1202 I2C driverr
Next by Date: Re: [PATCH v2 1/6] device property: document device_for_each_child_node macro
Previous by thread: [PATCH v2 1/6] device property: document device_for_each_child_node macro
Next by thread: Re: [PATCH v2 1/6] device property: document device_for_each_child_node macro
Index(es):
- Date
- Thread

[Index of Archives] [Linux ARM Kernel] [Linux ARM] [Linux Omap] [Fedora ARM] [IETF Annouce] [Security] [Bugtraq] [Linux OMAP] [Linux MIPS] [ECOS] [Asterisk Internet PBX] [Linux API]