From: Liam Girdwood <lrg@kernel.org>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: linux-kernel@vger.kernel.org, patches@opensource.wolfsonicro.com
Subject: Re: [PATCH] regulator: Remove supply_regulator_dev from machine configuration
Date: Mon, 09 May 2011 17:02:02 +0100 [thread overview]
Message-ID: <1304956922.3192.18.camel@odin> (raw)
In-Reply-To: <1304890218-19332-1-git-send-email-broonie@opensource.wolfsonmicro.com>
On Sun, 2011-05-08 at 22:30 +0100, Mark Brown wrote:
> supply_regulator_dev (using a struct pointer) has been deprecated in favour
> of supply_regulator (using a regulator name) for quite a few releases
> now with a warning generated if it is used and there are no current in tree
> users so just remove the code.
>
> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
> ---
Applied.
Thanks
Liam
prev parent reply other threads:[~2011-05-09 16:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-08 21:30 [PATCH] regulator: Remove supply_regulator_dev from machine configuration Mark Brown
2011-05-09 16:02 ` Liam Girdwood [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=1304956922.3192.18.camel@odin \
--to=lrg@kernel.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.wolfsonicro.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