From: Jason Yan <yanaijie@huawei.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Nishka Dasgupta <nishkadg.linux@gmail.com>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Hulk Robot <hulkci@huawei.com>,
Chris Brandt <Chris.Brandt@renesas.com>
Subject: Re: [PATCH] pinctrl: rza1: remove unused 'rza1l_swio_pins'
Date: Fri, 17 Apr 2020 18:35:36 +0800 [thread overview]
Message-ID: <76de8e85-d9a5-c58f-206e-15da59ee110e@huawei.com> (raw)
In-Reply-To: <CAMuHMdUfwbsfLNSxJLqkwTNEQims1RHBn_EwBvBUqEZshHZHdQ@mail.gmail.com>
在 2020/4/17 17:31, Geert Uytterhoeven 写道:
> Hi Jason,
>
> On Fri, Apr 17, 2020 at 10:54 AM Jason Yan <yanaijie@huawei.com> wrote:
>> Fix the following gcc warning:
>>
>> drivers/pinctrl/pinctrl-rza1.c:401:35: warning: ‘rza1l_swio_pins’
>> defined but not used [-Wunused-const-variable=]
>> static const struct rza1_swio_pin rza1l_swio_pins[] = {
>> ^~~~~~~~~~~~~~~
>>
>> Reported-by: Hulk Robot <hulkci@huawei.com>
>> Signed-off-by: Jason Yan <yanaijie@huawei.com>
>
> Thanks for your patch!
>
>> --- a/drivers/pinctrl/pinctrl-rza1.c
>> +++ b/drivers/pinctrl/pinctrl-rza1.c
>> @@ -398,15 +398,6 @@ static const struct rza1_bidir_pin rza1l_bidir_pins_p9[] = {
>> { .pin = 5, .func = 3 },
>> };
>>
>> -static const struct rza1_swio_pin rza1l_swio_pins[] = {
>> - { .port = 2, .pin = 8, .func = 2, .input = 0 },
>> - { .port = 5, .pin = 6, .func = 3, .input = 0 },
>> - { .port = 6, .pin = 6, .func = 3, .input = 0 },
>> - { .port = 6, .pin = 10, .func = 3, .input = 0 },
>> - { .port = 7, .pin = 10, .func = 2, .input = 0 },
>> - { .port = 8, .pin = 2, .func = 3, .input = 0 },
>> -};
>> -
>> static const struct rza1_bidir_entry rza1l_bidir_entries[RZA1_NPORTS] = {
>> [1] = { ARRAY_SIZE(rza1l_bidir_pins_p1), rza1l_bidir_pins_p1 },
>> [3] = { ARRAY_SIZE(rza1l_bidir_pins_p3), rza1l_bidir_pins_p3 },
>
> rza1l_swio_pins[] is unused because rza1l_swio_entries[] refers to the
> wrong array. So I'd rather see a patch to fix that instead.
>
Thanks for the explanation, I will send a new one.
> Thanks!
>
> Gr{oetje,eeting}s,
>
> Geert
>
next prev parent reply other threads:[~2020-04-17 10:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-17 9:20 Jason Yan
2020-04-17 9:31 ` Geert Uytterhoeven
2020-04-17 10:35 ` Jason Yan [this message]
2020-04-17 11:15 ` Chris Brandt
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=76de8e85-d9a5-c58f-206e-15da59ee110e@huawei.com \
--to=yanaijie@huawei.com \
--cc=Chris.Brandt@renesas.com \
--cc=geert@linux-m68k.org \
--cc=hulkci@huawei.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=nishkadg.linux@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
all inboxes | Powered by JetHome®