From: Chanwoo Choi <cw00.choi@samsung.com>
To: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
Cc: Lee Jones <lee.jones@linaro.org>,
Krzysztof Kozlowski <k.kozlowski@samsung.com>,
Samuel Ortiz <sameo@linux.intel.com>,
Olof Johansson <olof@lixom.net>,
Doug Anderson <dianders@chromium.org>,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] mfd: max77686: Remove unused struct max77686_opmode_data
Date: Thu, 07 May 2015 10:49:41 +0900 [thread overview]
Message-ID: <554AC4B5.2070905@samsung.com> (raw)
In-Reply-To: <1430932036-23971-1-git-send-email-javier.martinez@collabora.co.uk>
On 05/07/2015 02:07 AM, Javier Martinez Canillas wrote:
> The defined struct max77686_opmode_data isn't used neither by
> the max77686 mfd driver nor the drivers for its sub-devices.
>
> Signed-off-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
> ---
> include/linux/mfd/max77686.h | 5 -----
> 1 file changed, 5 deletions(-)
>
> diff --git a/include/linux/mfd/max77686.h b/include/linux/mfd/max77686.h
> index bb995ab9a575..d4b72d519115 100644
> --- a/include/linux/mfd/max77686.h
> +++ b/include/linux/mfd/max77686.h
> @@ -125,9 +125,4 @@ enum max77686_opmode {
> MAX77686_OPMODE_STANDBY,
> };
>
> -struct max77686_opmode_data {
> - int id;
> - int mode;
> -};
> -
> #endif /* __LINUX_MFD_MAX77686_H */
>
Reviewed-by: Chanwoo Choi <cw00.choi@samsung.com>
Thanks,
Chanwoo Choi
WARNING: multiple messages have this Message-ID (diff)
From: cw00.choi@samsung.com (Chanwoo Choi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] mfd: max77686: Remove unused struct max77686_opmode_data
Date: Thu, 07 May 2015 10:49:41 +0900 [thread overview]
Message-ID: <554AC4B5.2070905@samsung.com> (raw)
In-Reply-To: <1430932036-23971-1-git-send-email-javier.martinez@collabora.co.uk>
On 05/07/2015 02:07 AM, Javier Martinez Canillas wrote:
> The defined struct max77686_opmode_data isn't used neither by
> the max77686 mfd driver nor the drivers for its sub-devices.
>
> Signed-off-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
> ---
> include/linux/mfd/max77686.h | 5 -----
> 1 file changed, 5 deletions(-)
>
> diff --git a/include/linux/mfd/max77686.h b/include/linux/mfd/max77686.h
> index bb995ab9a575..d4b72d519115 100644
> --- a/include/linux/mfd/max77686.h
> +++ b/include/linux/mfd/max77686.h
> @@ -125,9 +125,4 @@ enum max77686_opmode {
> MAX77686_OPMODE_STANDBY,
> };
>
> -struct max77686_opmode_data {
> - int id;
> - int mode;
> -};
> -
> #endif /* __LINUX_MFD_MAX77686_H */
>
Reviewed-by: Chanwoo Choi <cw00.choi@samsung.com>
Thanks,
Chanwoo Choi
next prev parent reply other threads:[~2015-05-07 1:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-06 17:07 [PATCH 1/1] mfd: max77686: Remove unused struct max77686_opmode_data Javier Martinez Canillas
2015-05-06 17:07 ` Javier Martinez Canillas
2015-05-06 23:53 ` Krzysztof Kozlowski
2015-05-06 23:53 ` Krzysztof Kozlowski
2015-05-07 1:49 ` Chanwoo Choi [this message]
2015-05-07 1:49 ` Chanwoo Choi
2015-05-07 6:58 ` Lee Jones
2015-05-07 6:58 ` Lee Jones
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=554AC4B5.2070905@samsung.com \
--to=cw00.choi@samsung.com \
--cc=dianders@chromium.org \
--cc=javier.martinez@collabora.co.uk \
--cc=k.kozlowski@samsung.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=olof@lixom.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.