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: <20121004095803.26548bc7@endymion.delvare>
Date:	Thu, 4 Oct 2012 09:58:03 +0200
From:	Jean Delvare <khali@...ux-fr.org>
To:	Vivien Didelot <vivien.didelot@...oirfairelinux.com>
Cc:	linux-i2c@...r.kernel.org, Ben Dooks <ben-linux@...ff.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] i2c: correct struct i2c_driver doc about detection

Hi Vivien,

On Wed,  3 Oct 2012 16:17:24 -0400, Vivien Didelot wrote:
> s/address_data/address_list/ in addition to c3813d6.
> 
> Signed-off-by: Vivien Didelot <vivien.didelot@...oirfairelinux.com>
> ---
>  include/linux/i2c.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/include/linux/i2c.h b/include/linux/i2c.h
> index 8e25a91..8d87329 100644
> --- a/include/linux/i2c.h
> +++ b/include/linux/i2c.h
> @@ -140,7 +140,7 @@ extern s32 i2c_smbus_write_i2c_block_data(const struct i2c_client *client,
>   * The driver.owner field should be set to the module owner of this driver.
>   * The driver.name field should be set to the name of this driver.
>   *
> - * For automatic device detection, both @detect and @address_data must
> + * For automatic device detection, both @detect and @address_list must
>   * be defined. @class should also be set, otherwise only devices forced
>   * with module parameters will be created. The detect function must
>   * fill at least the name field of the i2c_board_info structure it is

Good catch! Applied, thanks.

-- 
Jean Delvare
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ