From: Lee Jones <lee.jones@linaro.org>
To: Krzysztof Kozlowski <k.kozlowski@samsung.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
linux-kernel@vger.kernel.org,
Samuel Ortiz <sameo@linux.intel.com>
Subject: Re: [PATCH 2/2] mfd: max77693: Remove unused structures
Date: Tue, 20 Jan 2015 15:18:09 +0000 [thread overview]
Message-ID: <20150120151809.GX13701@x1> (raw)
In-Reply-To: <1418981359-16457-3-git-send-email-k.kozlowski@samsung.com>
On Fri, 19 Dec 2014, Krzysztof Kozlowski wrote:
> The max77693 regulator driver no longer supports board files. Remove the
> left-overs. Additionally fix name of device in comment.
>
> Signed-off-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
> ---
> include/linux/mfd/max77693.h | 12 +-----------
> 1 file changed, 1 insertion(+), 11 deletions(-)
For my own reference:
Acked-by: Lee Jones <lee.jones@linaro.org>
> diff --git a/include/linux/mfd/max77693.h b/include/linux/mfd/max77693.h
> index f0b6585cd874..09a4dedaeea8 100644
> --- a/include/linux/mfd/max77693.h
> +++ b/include/linux/mfd/max77693.h
> @@ -30,7 +30,7 @@
> #ifndef __LINUX_MFD_MAX77693_H
> #define __LINUX_MFD_MAX77693_H
>
> -/* MAX77686 regulator IDs */
> +/* MAX77693 regulator IDs */
> enum max77693_regulators {
> MAX77693_ESAFEOUT1 = 0,
> MAX77693_ESAFEOUT2,
> @@ -38,12 +38,6 @@ enum max77693_regulators {
> MAX77693_REG_MAX,
> };
>
> -struct max77693_regulator_data {
> - int id;
> - struct regulator_init_data *initdata;
> - struct device_node *of_node;
> -};
> -
> struct max77693_reg_data {
> u8 addr;
> u8 data;
> @@ -103,10 +97,6 @@ struct max77693_led_platform_data {
> /* MAX77693 */
>
> struct max77693_platform_data {
> - /* regulator data */
> - struct max77693_regulator_data *regulators;
> - int num_regulators;
> -
> /* muic data */
> struct max77693_muic_platform_data *muic_data;
> struct max77693_led_platform_data *led_data;
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
prev parent reply other threads:[~2015-01-20 15:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-19 9:29 [PATCH 0/2] regulator: Simplify max77693 driver Krzysztof Kozlowski
2014-12-19 9:29 ` [PATCH 1/2] regulator: max77693: Let core parse DT and drop board files support Krzysztof Kozlowski
2014-12-19 9:29 ` [PATCH 2/2] mfd: max77693: Remove unused structures Krzysztof Kozlowski
2015-01-20 15:18 ` Lee Jones [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=20150120151809.GX13701@x1 \
--to=lee.jones@linaro.org \
--cc=broonie@kernel.org \
--cc=k.kozlowski@samsung.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sameo@linux.intel.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