lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAJZ5v0gxUbBj8iggT5e0YEwpRG=SpoN1t2MVss+i6-peBTDBEw@mail.gmail.com>
Date:   Tue, 7 Mar 2023 14:11:24 +0100
From:   "Rafael J. Wysocki" <rafael@...nel.org>
To:     Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc:     "Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
        linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org,
        "Rafael J. Wysocki" <rafael@...nel.org>,
        Len Brown <lenb@...nel.org>
Subject: Re: [PATCH v1 1/1] ACPI: docs: enumeration: Correct reference to the I²C device data type

On Thu, Mar 2, 2023 at 5:19 PM Andy Shevchenko
<andriy.shevchenko@...ux.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@...ux.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!

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ