From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
platform-driver-x86@vger.kernel.org,
"Hans de Goede" <hansg@kernel.org>,
"Linux ACPI" <linux-acpi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"Chen Yu" <yu.c.chen@intel.com>,
"Maximilian Luz" <luzmaximilian@gmail.com>
Subject: Re: [PATCH v1] platform/surface: surfacepro3_button: Stop setting acpi_device_name()
Date: Mon, 6 Jul 2026 18:46:51 +0300 [thread overview]
Message-ID: <akvN6-V7TOuwG4c2@ashevche-desk.local> (raw)
In-Reply-To: <6036011.DvuYhMxLoT@rafael.j.wysocki>
On Mon, Jul 06, 2026 at 02:28:56PM +0200, Rafael J. Wysocki wrote:
> Since acpi_device_name() set by the driver is only used for input
> class device name initialization and printing a message on probe
> success, and SURFACE_BUTTON_DEVICE_NAME can be used instead of it
> directly in both cases, make the driver do so and stop setting
> acpi_device_name().
>
> No intentional functional impact.
>
> This will facilitate the removal of device_name from struct
> acpi_device_pnp in the future.
...
> - input->name = acpi_device_name(device);
> + input->name = SURFACE_BUTTON_DEVICE_NAME;
> input->phys = button->phys;
> input->id.bustype = BUS_HOST;
> input->dev.parent = &pdev->dev;
> - dev_info(&pdev->dev, "%s [%s]\n", acpi_device_name(device),
> + dev_info(&pdev->dev, SURFACE_BUTTON_DEVICE_NAME " [%s]\n",
> acpi_device_bid(device));
I would keep one place of accessing the definition:
dev_info(&pdev->dev, "%s [%s]\n", input->name, acpi_device_bid(device));
If we ever change that, we won't need to look at two (or more) places.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-07-06 15:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 12:28 [PATCH v1] platform/surface: surfacepro3_button: Stop setting acpi_device_name() Rafael J. Wysocki
2026-07-06 15:32 ` Chen, Yu C
2026-07-06 15:46 ` Andy Shevchenko [this message]
2026-07-06 16:06 ` Rafael J. Wysocki (Intel)
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=akvN6-V7TOuwG4c2@ashevche-desk.local \
--to=andriy.shevchenko@linux.intel.com \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luzmaximilian@gmail.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=yu.c.chen@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