From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Jassi Brar <jassisinghbrar@gmail.com>
Cc: Vasily Khoruzhick <anarsoul@gmail.com>,
alsa-devel <alsa-devel@alsa-project.org>,
"Arnaud Patard (Rtp)" <arnaud.patard@rtp-net.org>,
Ben Dooks <ben-linux@fluff.org>,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH v2 1/1] ASoC: Add HP iPAQ H1940 support
Date: Mon, 13 Sep 2010 10:05:43 +0100 [thread overview]
Message-ID: <20100913090543.GG16606@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <AANLkTi=u08V3V70p9Prv5MVfqigFkeYggTAdh5Dx28NK@mail.gmail.com>
On Mon, Sep 13, 2010 at 10:09:16AM +0900, Jassi Brar wrote:
> Btw, sound/soc/soc-core.c is the real 'soc-audio' driver module not
> the MACHINE driver.
> Turns out, sound/soc/soc-core.c already has the
> MODULE_ALIAS("platform:soc-audio");
> So it seems like an immediate conflict.
Indeed - the MODULE_ALIAS() goes along with the device driver, not with
the registration of the device.
next prev parent reply other threads:[~2010-09-13 9:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-12 10:55 [PATCH] ASoC: Add HP iPAQ H1940 support Vasily Khoruzhick
2010-09-12 12:14 ` Jassi Brar
2010-09-12 12:15 ` Vasily Khoruzhick
2010-09-12 12:18 ` [PATCH v2 0/1] " Vasily Khoruzhick
2010-09-12 12:18 ` [PATCH v2 1/1] " Vasily Khoruzhick
2010-09-12 13:25 ` Marek Vasut
2010-09-12 17:07 ` Jassi Brar
2010-09-12 18:09 ` Vasily Khoruzhick
2010-09-13 1:09 ` Jassi Brar
2010-09-13 9:05 ` Mark Brown [this message]
2010-09-13 9:12 ` Vasily Khoruzhick
2010-09-13 9:47 ` [PATCH v3 0/1] " Vasily Khoruzhick
2010-09-13 9:47 ` [PATCH v3 1/1] " Vasily Khoruzhick
2010-09-20 10:38 ` Mark Brown
2010-09-27 7:47 ` [PATCH RESEND " Vasily Khoruzhick
2010-09-27 15:06 ` Mark Brown
2010-09-27 15:29 ` Vasily Khoruzhick
2010-10-15 7:49 ` Vasily khoruzhick
2010-10-15 11:37 ` Mark Brown
2010-10-15 12:52 ` Vasily khoruzhick
2010-09-13 9:07 ` [PATCH v2 " 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=20100913090543.GG16606@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=anarsoul@gmail.com \
--cc=arnaud.patard@rtp-net.org \
--cc=ben-linux@fluff.org \
--cc=jassisinghbrar@gmail.com \
--cc=lrg@slimlogic.co.uk \
/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.