[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0f6b04ea-c8e9-4fc5-b7c7-72080ed0c954@t-8ch.de>
Date: Fri, 13 Dec 2024 22:00:50 +0100
From: Thomas Weißschuh <linux@...ssschuh.net>
To: Armin Wolf <W_Armin@....de>
Cc: Sebastian Reichel <sre@...nel.org>,
Hans de Goede <hdegoede@...hat.com>, Benson Leung <bleung@...omium.org>,
Guenter Roeck <groeck@...omium.org>, linux-kernel@...r.kernel.org, chrome-platform@...ts.linux.dev,
linux-pm@...r.kernel.org
Subject: Re: [PATCH v6 0/4] power: supply: extension API
On 2024-12-12 15:27:52+0100, Armin Wolf wrote:
> Am 11.12.24 um 20:57 schrieb Thomas Weißschuh:
>
> > Introduce a mechanism for drivers to extend the properties implemented
> > by a power supply.
[..]
> > ---
> > Changes in v6:
> > - Drop alreay picked up ACPI battery hook rename patch
> > - Only return bool from power_supply_property_is_writeable()
> > - Improve naming for test_power symbols
> > - Integrate cros_charge-control fixes from the psy/fixes branch
> > - Add sysfs UAPI for extension discovery
> > - Use __must_check on API
> > - Make power_supply_for_each_extension() safer.
> > (And uglier, ideas welcome)
>
> Maybe we can use a do { ... } while (0) construct here.
I don't think so. The macro needs to expand to a dangling loop
condition. So whatever statement comes after gets executed in the loop.
[..]
Powered by blists - more mailing lists