From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: alsa-devel@alsa-project.org, Lars-Peter Clausen <lars@metafoo.de>,
Takashi Iwai <tiwai@suse.de>,
axel.lin@gmail.com, Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCH 1/2] sound: soc: add alias for tlv320aic3x
Date: Wed, 1 Feb 2012 12:39:48 +0000 [thread overview]
Message-ID: <20120201123947.GB17170@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CAMP44s2iq-RNNNNeFTZYBJbobEPE7sCOyduh=J--hhRghXkVJg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 649 bytes --]
On Wed, Feb 01, 2012 at 01:57:56PM +0200, Felipe Contreras wrote:
> On Wed, Feb 1, 2012 at 3:56 AM, Axel Lin <axel.lin@gmail.com> wrote:
> >> +MODULE_ALIAS("i2c:tlv320aic3x");
> > This is not required because "tlv320aic3x" is already in the aic3x_i2c_id table.
> > MODULE_DEVICE_TABLE will automatically setup this modalias.
> Since when? Last time I checked that was not the case. I will try
> again with v3.2 final, but I think on some of the rc's the alias
> wasn't there.
Since it was introduced, this is really nothing new (which is why you'll
not find I2C drivers with MODULE_ALIAS). This is the whole point of having
MODULE_DEVICE_TABLE.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2012-02-01 12:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 1:06 [PATCH 0/2] sound: soc: trivial stuff for tlv320aic3x Felipe Contreras
2012-02-01 1:06 ` [PATCH 1/2] sound: soc: add alias " Felipe Contreras
2012-02-01 1:56 ` Axel Lin
2012-02-01 11:57 ` Felipe Contreras
2012-02-01 12:39 ` Mark Brown [this message]
2012-02-01 1:06 ` [PATCH 2/2] sound: soc: tlv320aic3x: remove unused code Felipe Contreras
2012-02-06 16:44 ` Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120201123947.GB17170@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=axel.lin@gmail.com \
--cc=felipe.contreras@gmail.com \
--cc=lars@metafoo.de \
--cc=lrg@ti.com \
--cc=tiwai@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.