Re: [PATCH v4 1/2] gpiolib: Fix debug messaging in gpiod_find_and_request()

From: Bartosz Golaszewski
Date: Tue Mar 26 2024 - 07:59:03 EST


On Mon, Mar 25, 2024 at 6:18 PM Andy Shevchenko
<andriy.shevchenko@xxxxxxxxxxxxxxx> wrote:
>
> When consolidating GPIO lookups in ACPI code, the debug messaging
> had been reworked that the user may see
>
> [ 13.401147] (NULL device *): using ACPI '\_SB.LEDS.led-0' for '(null)' GPIO lookup
> [ 13.401378] gpio gpiochip0: Persistence not supported for GPIO 40
> [ 13.401402] gpio-40 (?): no flags found for (null)
>
> instead of
>
> [ 14.182962] gpio gpiochip0: Persistence not supported for GPIO 40
> [ 14.182994] gpio-40 (?): no flags found for gpios
>
> The '(null)' parts are less informative and likely scare the users.
> Replace them by '(default)' which can point out to the default connection
> IDs, such as 'gpios'.
>
> While at it, amend other places where con_id is used in the messages.
>
> Reported-by: Ferry Toth <ftoth@xxxxxxxxxxxxxx>
> Fixes: 8eb1f71e7acc ("gpiolib: consolidate GPIO lookups")
> Suggested-by: Dmitry Torokhov <dmitry.torokhov@xxxxxxxxx>
> Tested-by: Ferry Toth <ftoth@xxxxxxxxxxxxxx>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
> ---

I queued this one for fixes. I will take patch 2/2 through the
for-next tree as it's not really a fix.

Bart