linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linus.walleij@linaro.org (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] pinctrl: zte: fix dereference of 'data' in zx_set_mux()
Date: Mon, 31 Jul 2017 15:13:40 +0200	[thread overview]
Message-ID: <CACRpkda31aW5YpFefGe3R8mWmMJ-iPF7UMB8t-tqPxhnihkWEw@mail.gmail.com> (raw)
In-Reply-To: <1498880736-18143-1-git-send-email-shawnguo@kernel.org>

On Sat, Jul 1, 2017 at 5:45 AM, Shawn Guo <shawnguo@kernel.org> wrote:

> From: Shawn Guo <shawn.guo@linaro.org>
>
> It fixes the following Smatch complaint:
>
> drivers/pinctrl/zte/pinctrl-zx.c:76 zx_set_mux()
> warn: variable dereferenced before check 'data' (see line 67)
>
> Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
> Fixes: cbff0c4d27f4 ("pinctrl: add ZTE ZX pinctrl driver support")
> Signed-off-by: Shawn Guo <shawn.guo@linaro.org>

Patch applied for fixes.

Yours,
Linus Walleij

      reply	other threads:[~2017-07-31 13:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-01  3:45 [PATCH] pinctrl: zte: fix dereference of 'data' in zx_set_mux() Shawn Guo
2017-07-31 13:13 ` Linus Walleij [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=CACRpkda31aW5YpFefGe3R8mWmMJ-iPF7UMB8t-tqPxhnihkWEw@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).