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] [thread-next>] [day] [month] [year] [list]
Message-ID: <s5hk2sjbrga.wl-tiwai@suse.de>
Date:	Tue, 25 Aug 2015 12:19:49 +0200
From:	Takashi Iwai <tiwai@...e.de>
To:	"Javier Martinez Canillas" <javier@....samsung.com>
Cc:	<linux-kernel@...r.kernel.org>, <alsa-devel@...a-project.org>,
	"Jaroslav Kysela" <perex@...ex.cz>,
	"Wolfram Sang" <wsa@...-dreams.de>
Subject: Re: [RESEND PATCH 4/7] ALSA: ppc: keywest: Export I2C module alias information

On Tue, 25 Aug 2015 08:31:14 +0200,
Javier Martinez Canillas wrote:
> 
> The I2C core always reports the MODALIAS uevent as "i2c:<client name"
> regardless if the driver was matched using the I2C id_table or the
> of_match_table. So the driver needs to export the I2C table and this
> be built into the module or udev won't have the necessary information
> to auto load the correct module when the device is added.
> 
> Signed-off-by: Javier Martinez Canillas <javier@....samsung.com>

Applied, thanks.


Takashi

> 
> ---
> 
>  sound/ppc/keywest.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/sound/ppc/keywest.c b/sound/ppc/keywest.c
> index 6120a067494a..f644a8c57e0a 100644
> --- a/sound/ppc/keywest.c
> +++ b/sound/ppc/keywest.c
> @@ -101,6 +101,7 @@ static const struct i2c_device_id keywest_i2c_id[] = {
>  	{ "keywest", 0 },		/* instantiated by us if needed */
>  	{ }
>  };
> +MODULE_DEVICE_TABLE(i2c, keywest_i2c_id);
>  
>  static struct i2c_driver keywest_driver = {
>  	.driver = {
> -- 
> 2.4.3
> 
> .
> 
--
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