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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 18 Jun 2012 19:15:46 +0200
From:	Roland Stigge <stigge@...com.de>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
CC:	swarren@...dotorg.org, cjb@...top.org, grant.likely@...retlab.ca,
	rob.herring@...xeda.com, rmk+kernel@....linux.org.uk,
	ulf.hansson@...ricsson.com, linus.walleij@...aro.org,
	linux-mmc@...r.kernel.org, linux-kernel@...r.kernel.org,
	aletes.xgr@...il.com, linux-arm-kernel@...ts.infradead.org,
	lrg@...com, perex@...ex.cz, tiwai@...e.de,
	alsa-devel@...a-project.org
Subject: Re: [PATCH 1/2] sound: tegra_wm8903: Adjust to of_get_named_gpio()
 change

On 06/18/2012 07:04 PM, Mark Brown wrote:
> On Mon, Jun 18, 2012 at 07:00:14PM +0200, Roland Stigge wrote:
> 
>> Basically, yes. But this would mean that doing via gpio, we would
>> need to pull other stuff from the sound tree over to gpio to
>> build upon because "my" tegra_* sound patches won't apply to the
>> gpio branch currently.
> 
> Oh, yes.  Stephen's gone and reorganised all that code which means
> it's not a trivial merge.  Ho hum.  I'm happy to apply them if
> folks are comfortable with it, I guess ideally I'd be able to pull
> a branch with the gpio changes in and then apply on top of that.

Depending on what else changes will come via gpio for 3.6, maybe you
don't even need to merge gpio to sound?

Can you please coordinate between sound and gpio?

Thanks in advance!

Roland

PS: I'm posting a combined patch suitable for the sound subsystem.
Please tell me if you also need the gpiolib-of patch singled out.
--
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