linux-kernel - Re: [PATCH 1/3] regulator: core: Add devres versions of notifier registration

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] [day] [month] [year] [list]

Message-ID: <20150305165839.GR21293@sirena.org.uk>
Date:	Thu, 5 Mar 2015 16:58:39 +0000
From:	Mark Brown <broonie@...nel.org>
To:	Charles Keepax <ckeepax@...nsource.wolfsonmicro.com>
Cc:	lgirdwood@...il.com, info@...zy-audio.com,
	alsa-devel@...a-project.org, linux-kernel@...r.kernel.org,
	patches@...nsource.wolfsonmicro.com
Subject: Re: [PATCH 1/3] regulator: core: Add devres versions of notifier
 registration

On Thu, Mar 05, 2015 at 03:39:20PM +0000, Charles Keepax wrote:
> From: Charles Keepax <ckeepax@...il.com>
> 
> Add devm_regulator_register_notifier, this adds the resource against the
> device for the consumer supply we are registering the notifier for. There
> seem to be few use-cases where this wouldn't be the users intention and
> this ensures the notifiers will always be removed at the correct time.

Applied all, thanks.

> I have based this series of your ASoC tree Mark, because the
> wm8804 patches have dependencies there. But just let me know
> if you would rather I send the regulator patch against your
> regulator tree.

You should send against the relevant tree for the subsystem usually, but
in this case they're the same as there's no relevant regulator changes.

Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)