From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Chen Yu" <yu.c.chen@intel.com>,
"Hans de Goede" <hansg@kernel.org>,
platform-driver-x86@vger.kernel.org,
"Maximilian Luz" <luzmaximilian@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
"Linux ACPI" <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH v1] platform/surface: surfacepro3_button: Check ACPI_COMPANION()
Date: Tue, 12 May 2026 19:41:55 +0300 [thread overview]
Message-ID: <agNYU8Q7Aa9Nm_V2@ashevche-desk.local> (raw)
In-Reply-To: <23119222.EfDdHjke4D@rafael.j.wysocki>
On Tue, May 12, 2026 at 06:30:26PM +0200, Rafael J. Wysocki wrote:
> Every platform driver can be forced to match a device that doesn't match
> its list of device IDs because of device_match_driver_override(), so
> platform drivers that rely on the existence of a device's ACPI companion
> object need to verify its presence.
>
> Accordingly, add a requisite ACPI_COMPANION() check against NULL to the
> surfacepro3_button driver.
Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
...
> strscpy(acpi_device_name(device), SURFACE_BUTTON_DEVICE_NAME);
> - snprintf(button->phys, sizeof(button->phys), "%s/buttons", hid);
> + snprintf(button->phys, sizeof(button->phys), "%s/buttons",
> + acpi_device_hid(device));
I'm wondering if some CIs will now generate a snprintf() warning
(this was in the original code if the compiler can prove no truncation
of the string, though).
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-05-12 16:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 16:30 [PATCH v1] platform/surface: surfacepro3_button: Check ACPI_COMPANION() Rafael J. Wysocki
2026-05-12 16:41 ` Andy Shevchenko [this message]
2026-05-12 16:44 ` Rafael J. Wysocki
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=agNYU8Q7Aa9Nm_V2@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