* [PATCH v1 1/1] ACPI: docs: enumeration: Correct reference to the I²C device data type
@ 2023-03-02 16:12 Andy Shevchenko
2023-03-07 13:11 ` Rafael J. Wysocki
0 siblings, 1 reply; 2+ messages in thread
From: Andy Shevchenko @ 2023-03-02 16:12 UTC (permalink / raw)
To: Andy Shevchenko, Rafael J. Wysocki, linux-acpi, linux-kernel
Cc: Rafael J. Wysocki, Len Brown
I²C peripheral devices that are connected to the controller are
represented in the Linux kernel as objects of the struct i2c_client.
Fix this in the documentation.
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
---
Documentation/firmware-guide/acpi/enumeration.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/firmware-guide/acpi/enumeration.rst b/Documentation/firmware-guide/acpi/enumeration.rst
index b9dc0c603f36..56d9913a3370 100644
--- a/Documentation/firmware-guide/acpi/enumeration.rst
+++ b/Documentation/firmware-guide/acpi/enumeration.rst
@@ -19,7 +19,7 @@ possible we decided to do following:
platform devices.
- Devices behind real busses where there is a connector resource
- are represented as struct spi_device or struct i2c_device. Note
+ are represented as struct spi_device or struct i2c_client. Note
that standard UARTs are not busses so there is no struct uart_device,
although some of them may be represented by struct serdev_device.
--
2.39.1
^ permalink raw reply [flat|nested] 2+ messages in thread* Re: [PATCH v1 1/1] ACPI: docs: enumeration: Correct reference to the I²C device data type
2023-03-02 16:12 [PATCH v1 1/1] ACPI: docs: enumeration: Correct reference to the I²C device data type Andy Shevchenko
@ 2023-03-07 13:11 ` Rafael J. Wysocki
0 siblings, 0 replies; 2+ messages in thread
From: Rafael J. Wysocki @ 2023-03-07 13:11 UTC (permalink / raw)
To: Andy Shevchenko
Cc: Rafael J. Wysocki, linux-acpi, linux-kernel, Rafael J. Wysocki,
Len Brown
On Thu, Mar 2, 2023 at 5:19 PM Andy Shevchenko
<andriy.shevchenko@linux.intel.com> wrote:
>
> I²C peripheral devices that are connected to the controller are
> represented in the Linux kernel as objects of the struct i2c_client.
> Fix this in the documentation.
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
> Documentation/firmware-guide/acpi/enumeration.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/firmware-guide/acpi/enumeration.rst b/Documentation/firmware-guide/acpi/enumeration.rst
> index b9dc0c603f36..56d9913a3370 100644
> --- a/Documentation/firmware-guide/acpi/enumeration.rst
> +++ b/Documentation/firmware-guide/acpi/enumeration.rst
> @@ -19,7 +19,7 @@ possible we decided to do following:
> platform devices.
>
> - Devices behind real busses where there is a connector resource
> - are represented as struct spi_device or struct i2c_device. Note
> + are represented as struct spi_device or struct i2c_client. Note
> that standard UARTs are not busses so there is no struct uart_device,
> although some of them may be represented by struct serdev_device.
>
> --
Applied as 6.3-rc material, thanks!
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2023-03-07 13:14 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-03-02 16:12 [PATCH v1 1/1] ACPI: docs: enumeration: Correct reference to the I²C device data type Andy Shevchenko
2023-03-07 13:11 ` Rafael J. Wysocki
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome