Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 1a147ed7 authored by Mathias Krause's avatar Mathias Krause Committed by Rafael J. Wysocki
Browse files

ACPI: Constify ACPI device IDs in documentation 



ACPI device ID arrays normally don't need to be written to as they're
only ever read. The common usage -- embedding pointers to acpi_device_id
arrays in other data structures -- reference them as 'const', e.g. as in
struct acpi_driver / acpi_scan_handler / device_driver. The matchers are
taking const pointers, too. So it's only natural, to propose using const
arrays. Change the documentation accordingly.

Signed-off-by: default avatarMathias Krause <minipli@googlemail.com>
Signed-off-by: default avatarRafael J. Wysocki <rafael.j.wysocki@intel.com>
parent eb348664

Documentation/acpi/enumeration.txt

+3 −3
Original line number Diff line number Diff line
@@ -42,7 +42,7 @@ Adding ACPI support for an existing driver should be pretty 
straightforward. Here is the simplest example:



	#ifdef CONFIG_ACPI

	static struct acpi_device_id mydrv_acpi_match[] = {

	static const struct acpi_device_id mydrv_acpi_match[] = {

		/* ACPI IDs here */

		{ }

	};
@@ -166,7 +166,7 @@ the platform device drivers. Below is an example where we add ACPI support 
to at25 SPI eeprom driver (this is meant for the above ACPI snippet):



	#ifdef CONFIG_ACPI

	static struct acpi_device_id at25_acpi_match[] = {

	static const struct acpi_device_id at25_acpi_match[] = {

		{ "AT25", 0 },

		{ },

	};
@@ -230,7 +230,7 @@ Below is an example of how to add ACPI support to the existing mpu3050 
input driver:



	#ifdef CONFIG_ACPI

	static struct acpi_device_id mpu3050_acpi_match[] = {

	static const struct acpi_device_id mpu3050_acpi_match[] = {

		{ "MPU3050", 0 },

		{ },

	};