From: Shyam Sundar S K <ssundark@amd.com>
To: Linus Walleij <linus.walleij@linaro.org>, Arnd Bergmann <arnd@arndb.de>
Cc: "Agrawal, Nitesh-kumar" <Nitesh-kumar.Agrawal@amd.com>,
Pankaj Sen <Pankaj.Sen@amd.com>,
"Shah, Nehal-bakulchandra" <Nehal-Bakulchandra.shah@amd.com>,
Shyam-sundar S-k <Shyam-sundar.S-k@amd.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] pinctrl: amd: avoid maybe-uninitalized warning
Date: Thu, 12 Jan 2017 13:45:08 +0530 [thread overview]
Message-ID: <2d8a7eeb-f49a-47eb-1b74-70631c27e931@amd.com> (raw)
In-Reply-To: <CACRpkdZrhrMi4SGa8RCwTzcLQDumEQjpw+LftLNEaxxRAZu8Vw@mail.gmail.com>
Hi Linus,
You have already added patch for the same "[PATCH] pinctrl: amd: fix compilation warning" and applied to one of your fixed branch.
Do you feel this patch needs to be taken ?
Thanks,
Shyam
On 1/12/2017 1:19 PM, Linus Walleij wrote:
> On Wed, Jan 11, 2017 at 3:36 PM, Arnd Bergmann <arnd@arndb.de> wrote:
>
>> Since gpio_dev->hwbank_num is now a variable, the compiler cannot
>> figure out if pin_num is initialized at all:
>>
>> drivers/pinctrl/pinctrl-amd.c: In function 'amd_gpio_dbg_show':
>> drivers/pinctrl/pinctrl-amd.c:210:3: warning: 'pin_num' may be used uninitialized in this function [-Wmaybe-uninitialized]
>> for (; i < pin_num; i++) {
>> ^~~
>> drivers/pinctrl/pinctrl-amd.c:172:21: warning: 'i' may be used uninitialized in this function [-Wmaybe-uninitialized]
>>
>> This adds a 'default' statement to make that case well-defined.
>>
>> Fixes: 3bfd44306c65 ("pinctrl: amd: Add support for additional GPIO")
>> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
>
> Patch applied.
>
> Yours,
> Linus Walleij
>
prev parent reply other threads:[~2017-01-12 8:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 14:36 Arnd Bergmann
2017-01-12 7:49 ` Linus Walleij
2017-01-12 8:15 ` Shyam Sundar S K [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=2d8a7eeb-f49a-47eb-1b74-70631c27e931@amd.com \
--to=ssundark@amd.com \
--cc=Nehal-Bakulchandra.shah@amd.com \
--cc=Nitesh-kumar.Agrawal@amd.com \
--cc=Pankaj.Sen@amd.com \
--cc=Shyam-sundar.S-k@amd.com \
--cc=arnd@arndb.de \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®