linux-kernel - Re: [PATCH 4/4] ASoC: TWL4030: Driver registration via twl4030

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]

Date:	Tue, 20 Oct 2009 15:01:28 +0300
From:	Peter Ujfalusi <peter.ujfalusi@...ia.com>
To:	ext Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc:	"alsa-devel@...a-project.org" <alsa-devel@...a-project.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-omap@...r.kernel.org" <linux-omap@...r.kernel.org>,
	"sameo@...ux.intel.com" <sameo@...ux.intel.com>,
	"tony@...mide.com" <tony@...mide.com>
Subject: Re: [PATCH 4/4] ASoC: TWL4030: Driver registration via twl4030_codec MFD

On Tuesday 20 October 2009 14:51:06 ext Mark Brown wrote:
> Sure, though I suspect patch 3 could just be split in two happily with
> an include.  I don't really mind either way.  If you are going to keep
> them as one patch it'd be good to call out the move in the changelog.

I'll split the soc codec patch to two, one is changing the header the other is 
for the change in the codec driver.

> That's a good enough reason to leave things as they are, though really
> if you're building SND_SOC_ALL_CODECs in a production system you're
> being a bit strange.

Fair enough.

> >
> >  +MODULE_ALIAS("platform:twl4030_codec_audio");
> 
> Yes.  The aliasing makes no reference to the parents of the device, it
> only cares about the device name - for the purposes of module loading
> and driver matching it's identical to any other platform device.

Good to know, I'll change this as well.

Thanks,
Péter
--
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/