From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Linux ACPI" <linux-acpi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Hans de Goede" <hansg@kernel.org>,
platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH v1] ACPI: bus: Drop two fields from struct acpi_device_pnp
Date: Tue, 1 Sep 2026 10:45:23 +0300 [thread overview]
Message-ID: <apaCk3qmZ5hO_aNC@ashevche-desk.local> (raw)
In-Reply-To: <6314925.lOV4Wx5bFT@rafael.j.wysocki>
On Mon, Aug 31, 2026 at 10:07:10PM +0200, Rafael J. Wysocki wrote:
> There are two fields in struct acpi_device_pnp, device_name and
> device_class, that were supposed to be populated and used by device
> drivers, but they have never been used consistently and now they
> are only set for the bus object in acpi_set_pnp_ids() (and never
> read afterward).
>
> Drop them along with all of the associated symbols except for
> MAX_ACPI_CLASS_NAME_LEN and the acpi_device_class typedef that
> are used by the ACPI netlink messaging code. Move those two
> definitions closer to the struct acpi_bus_event that refers to
> the acpi_device_class type.
Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
...
> +#define MAX_ACPI_CLASS_NAME_LEN 20
> +typedef char acpi_device_class[MAX_ACPI_CLASS_NAME_LEN];
Are you planning to use this in some future code?
> struct acpi_bus_event {
> struct list_head node;
> acpi_device_class device_class;
Otherwise I would go with complete replacement of the above to simple
char acpi_device_class[20];
here.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-09-01 7:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 20:07 Rafael J. Wysocki
2026-08-31 20:11 ` Hans de Goede
2026-09-01 7:45 ` Andy Shevchenko [this message]
2026-09-01 16:31 ` 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=apaCk3qmZ5hO_aNC@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=platform-driver-x86@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
all inboxes | Powered by JetHome®