From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Linux ACPI <linux-acpi@vger.kernel.org>,
Bjorn Helgaas <helgaas@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1] PNP: ACPI: Stop using acpi_device_name()
Date: Wed, 8 Jul 2026 17:39:25 +0300 [thread overview]
Message-ID: <ak5hHUpQsFyn04N9@ashevche-desk.local> (raw)
In-Reply-To: <23191780.EfDdHjke4D@rafael.j.wysocki>
On Mon, Jul 06, 2026 at 02:43:32PM +0200, Rafael J. Wysocki wrote:
> Since acpi_device_name() checked by pnpacpi_add_device() is never
> populated, its length is always zero and the codition checking it
> is always false.
>
> Accordingly, drop that condition and use acpi_device_bid(device) for
> setting dev->name in pnpacpi_add_device() unconditionally.
>
> No intentional functional impact.
>
> This will facilitate the removal of device_name from struct
> acpi_device_pnp in the future.
Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
...
> - if (strlen(acpi_device_name(device)))
> - strscpy(dev->name, acpi_device_name(device), sizeof(dev->name));
> - else
> - strscpy(dev->name, acpi_device_bid(device), sizeof(dev->name));
> + strscpy(dev->name, acpi_device_bid(device), sizeof(dev->name));
'dev' here is of struct pnp_dev, so this is the way to fill it.
(I was first confused, but after looking into the full context
everything becomes clear.)
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2026-07-08 14:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 12:43 [PATCH v1] PNP: ACPI: Stop using acpi_device_name() Rafael J. Wysocki
2026-07-08 14:39 ` Andy Shevchenko [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=ak5hHUpQsFyn04N9@ashevche-desk.local \
--to=andriy.shevchenko@linux.intel.com \
--cc=helgaas@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
/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