linux-kernel - Re: linux-next: manual merge of the sound-asoc tree with the i.MX tree

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:	Wed, 29 Sep 2010 23:58:13 -0700
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Uwe Kleine-König 
	<u.kleine-koenig@...gutronix.de>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	Liam Girdwood <lrg@...mlogic.co.uk>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Sascha Hauer <s.hauer@...gutronix.de>
Subject: Re: linux-next: manual merge of the sound-asoc tree with the i.MX
 tree

On Thu, Sep 30, 2010 at 08:45:33AM +0200, Uwe Kleine-König wrote:

> I might be wrong, but I think there are no non-audio users of the ssi
> device?

That's kind of the point; while this is a generic serial port I've never
seen it used for anything except audio.

> I think the correct fix is to squash the patch I just sent into the
> commit merging the two.

If there's no non-audio users there's no need to do the rename - the
renames are to avoid having the ASoC DAI drivers suddenly start binding
with other drivers so we could just revert the rename in ASoC which
would remove the merge issue.
--
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/