From: Lee Jones <lee.jones@linaro.org>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] mfd: lm3533: fix build warning
Date: Tue, 13 Oct 2015 09:45:03 +0100 [thread overview]
Message-ID: <20151013084503.GC32409@x1> (raw)
In-Reply-To: <1444220929-18949-1-git-send-email-sudipm.mukherjee@gmail.com>
On Wed, 07 Oct 2015, Sudip Mukherjee wrote:
> We were getting build warning about unused variable 'ret'.
> The commit c749db571dcf has removed the use of ret but missed removing
> the variable which is unused now.
>
> Fixes: c749db571dcf ("mfd: lm3533: Simplify function return logic")
> Signed-off-by: Sudip Mukherjee <sudip@vectorindia.org>
> ---
> drivers/mfd/lm3533-core.c | 1 -
> 1 file changed, 1 deletion(-)
Applied, thanks.
> diff --git a/drivers/mfd/lm3533-core.c b/drivers/mfd/lm3533-core.c
> index 193ecee1..5abcbb2 100644
> --- a/drivers/mfd/lm3533-core.c
> +++ b/drivers/mfd/lm3533-core.c
> @@ -592,7 +592,6 @@ static int lm3533_i2c_probe(struct i2c_client *i2c,
> const struct i2c_device_id *id)
> {
> struct lm3533 *lm3533;
> - int ret;
>
> dev_dbg(&i2c->dev, "%s\n", __func__);
>
--
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-10-13 8:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 12:28 [PATCH 1/2] mfd: lm3533: fix build warning Sudip Mukherjee
2015-10-07 12:28 ` [PATCH 2/2] mfd: rtsx: " Sudip Mukherjee
2015-10-07 12:40 ` kbuild test robot
2015-10-07 12:46 ` Sudip Mukherjee
2015-10-07 13:48 ` [kbuild-all] " Fengguang Wu
2015-10-07 15:41 ` Sudip Mukherjee
2015-10-08 0:56 ` Fengguang Wu
2015-10-08 6:30 ` Greg KH
2015-10-08 7:45 ` Sudip Mukherjee
2015-10-13 8:45 ` Lee Jones
2015-10-07 12:41 ` [PATCH 1/2] mfd: lm3533: " kbuild test robot
2015-10-13 8:45 ` 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=20151013084503.GC32409@x1 \
--to=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.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