From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Prashant Malani <pmalani@chromium.org>,
linux-acpi@vger.kernel.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 2/5] acpi: Store CRC-32 hash of the _PLD in struct acpi_device
Date: Wed, 22 Dec 2021 20:28:17 +0200 [thread overview]
Message-ID: <YcNuQYfbMcxlRkSP@smile.fi.intel.com> (raw)
In-Reply-To: <20211222143258.82305-3-heikki.krogerus@linux.intel.com>
On Wed, Dec 22, 2021 at 05:32:55PM +0300, Heikki Krogerus wrote:
> Storing CRC-32 hash of the Physical Location of Device
> object (_PLD) with devices that have it. The hash is stored
> to a new struct acpi_device member "pld_crc".
>
> The hash makes it easier to find devices that share a
> location, as there is no need to evaluate the entire object
> every time. Knowledge about devices that share a location
> can be used in device drivers that need to know the
> connections to other components inside a system. USB3 ports
> will for example always share their location with a USB2
> port.
...
> @@ -739,7 +752,6 @@ static inline void acpi_bus_put_acpi_device(struct acpi_device *adev)
>
> static inline int register_acpi_bus_type(void *bus) { return 0; }
> static inline int unregister_acpi_bus_type(void *bus) { return 0; }
> -
> #endif /* CONFIG_ACPI */
Looks like a stray change.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2021-12-22 18:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-22 14:32 [PATCH v4 0/5] acpi: Store _PLD information and convert users Heikki Krogerus
2021-12-22 14:32 ` [PATCH v4 1/5] acpi: Export acpi_bus_type Heikki Krogerus
2021-12-22 14:32 ` [PATCH v4 2/5] acpi: Store CRC-32 hash of the _PLD in struct acpi_device Heikki Krogerus
2021-12-22 16:55 ` Rafael J. Wysocki
2021-12-23 8:04 ` Heikki Krogerus
2021-12-22 18:28 ` Andy Shevchenko [this message]
2021-12-22 14:32 ` [PATCH v4 3/5] usb: Link the ports to the connectors they are attached to Heikki Krogerus
2021-12-22 14:32 ` [PATCH v4 4/5] usb: typec: port-mapper: Convert to the component framework Heikki Krogerus
2021-12-22 14:32 ` [PATCH v4 5/5] usb: Remove usb_for_each_port() Heikki Krogerus
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=YcNuQYfbMcxlRkSP@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=pmalani@chromium.org \
--cc=rafael@kernel.org \
--cc=sakari.ailus@linux.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