From: Stephen Warren <swarren@wwwdotorg.org>
To: Richard Genoud <richard.genoud@gmail.com>
Cc: Jiri Kosina <trivial@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] trivial: pinctrl core: remove extraneous code lines
Date: Fri, 10 Aug 2012 09:20:53 -0600 [thread overview]
Message-ID: <502526D5.3080002@wwwdotorg.org> (raw)
In-Reply-To: <1344610429-12607-1-git-send-email-richard.genoud@gmail.com>
On 08/10/2012 08:53 AM, Richard Genoud wrote:
> In function pinctrl_get_locked, pointer p is returned on error, and also
> return on no_error.
> So, we just return it with no error test.
>
> It's pretty the same in function pinctrl_lookup_state_locked: state is
> returned in every case, so we drop the error test and just return state.
>
> Signed-off-by: Richard Genoud <richard.genoud@gmail.com>
> ---
> drivers/pinctrl/core.c | 10 ++--------
> 1 files changed, 2 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/pinctrl/core.c b/drivers/pinctrl/core.c
> index fb7f3be..7365d46 100644
> --- a/drivers/pinctrl/core.c
> +++ b/drivers/pinctrl/core.c
> @@ -657,11 +657,7 @@ static struct pinctrl *pinctrl_get_locked(struct device *dev)
> if (p != NULL)
> return ERR_PTR(-EBUSY);
>
> - p = create_pinctrl(dev);
> - if (IS_ERR(p))
> - return p;
> -
> - return p;
> + return create_pinctrl(dev);
> }
This makes sense.
> /**
> @@ -738,10 +734,8 @@ static struct pinctrl_state *pinctrl_lookup_state_locked(struct pinctrl *p,
> dev_dbg(p->dev, "using pinctrl dummy state (%s)\n",
> name);
> state = create_state(p, name);
> - if (IS_ERR(state))
> - return state;
> } else {
> - return ERR_PTR(-ENODEV);
> + state = ERR_PTR(-ENODEV);
> }
> }
Personally I find the code much clearer as it is, but the result of this
patch still looks correct.
next prev parent reply other threads:[~2012-08-10 15:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-10 14:53 [PATCH] trivial: pinctrl core: remove extraneous code lines Richard Genoud
2012-08-10 15:20 ` Stephen Warren [this message]
2012-08-13 14:07 ` Linus Walleij
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=502526D5.3080002@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richard.genoud@gmail.com \
--cc=trivial@kernel.org \
/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