From: Mark Brown <broonie@kernel.org>
To: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Cc: lgirdwood@gmail.com, info@crazy-audio.com,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH 1/3] regulator: core: Add devres versions of notifier registration
Date: Thu, 5 Mar 2015 16:58:39 +0000 [thread overview]
Message-ID: <20150305165839.GR21293@sirena.org.uk> (raw)
In-Reply-To: <1425569962-14285-1-git-send-email-ckeepax@opensource.wolfsonmicro.com>
[-- Attachment #1: Type: text/plain, Size: 800 bytes --]
On Thu, Mar 05, 2015 at 03:39:20PM +0000, Charles Keepax wrote:
> From: Charles Keepax <ckeepax@gmail.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.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2015-03-05 16:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 15:39 Charles Keepax
2015-03-05 15:39 ` [PATCH 2/3] ASoC: wm8804: Use new devres regulator_register_notifier Charles Keepax
2015-03-05 15:39 ` [PATCH 3/3] ASoC: wm8804: Fix small issues in probe error paths Charles Keepax
2015-03-05 16:58 ` Mark Brown [this message]
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=20150305165839.GR21293@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=info@crazy-audio.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®