From: Colin Ian King <colin.king@canonical.com>
To: Rob Herring <robh@kernel.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Nishanth Menon <nm@ti.com>, Lokesh Vutla <lokeshvutla@ti.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][V2] pinctrl: ti-iodelay: remove redundant pin < 0 check on unsigned int
Date: Mon, 16 Jan 2017 15:52:04 +0000 [thread overview]
Message-ID: <7cc8f5f0-7899-ca16-2bbb-8869abfda650@canonical.com> (raw)
In-Reply-To: <CAL_JsqKoRr+VrtgNNHCTH5492N9k+sgiGhX778OEAmsYT7wYjw@mail.gmail.com>
On 16/01/17 15:45, Rob Herring wrote:
> On Fri, Jan 13, 2017 at 3:06 PM, Colin King <colin.king@canonical.com> wrote:
>> From: Colin Ian King <colin.king@canonical.com>
>>
>> pin is an unsigned int and therefore can never be < 0 so
>> this check is redundant. Remove the check and the associated
>> dev_err error message.
>
> Not sure why I got copied on this...
>
>> Fixes CoverityScan CID#1396438 ("Unsigned compared against 0")
>>
>> Signed-off-by: Colin Ian King <colin.king@canonical.com>
>> ---
>> drivers/pinctrl/ti/pinctrl-ti-iodelay.c | 6 ------
>
> This file doesn't exist in mainline.
>
>> 1 file changed, 6 deletions(-)
>>
>> diff --git a/drivers/pinctrl/ti/pinctrl-ti-iodelay.c b/drivers/pinctrl/ti/pinctrl-ti-iodelay.c
>> index 3b86d3d..a345166 100644
>> --- a/drivers/pinctrl/ti/pinctrl-ti-iodelay.c
>> +++ b/drivers/pinctrl/ti/pinctrl-ti-iodelay.c
>> @@ -665,12 +665,6 @@ static void ti_iodelay_pin_dbg_show(struct pinctrl_dev *pctldev,
>> r = iod->reg_data;
>>
>> offset = ti_iodelay_pin_to_offset(iod, pin);
>> - if (pin < 0) {
>
> Shouldn't this be "if (offset < 0)"?
Yep. However if the code was correct and using offset:
if (offset < 0) {
...
then we still get the same issue, that is, offset is unsigned so that
comparison is redundant since it can't be < 0. Perhaps I should re-send
a V3 with an updated commit message.
>
>
>> - dev_err(iod->dev, "invalid pin offset for pin%i\n", pin);
>> -
>> - return;
>> - }
>> -
>> pd = &iod->pa[pin];
>> cfg = pd->drv_data;
>>
>> --
>> 2.10.2
>>
prev parent reply other threads:[~2017-01-16 15:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-13 21:06 Colin King
2017-01-14 16:48 ` Nishanth Menon
2017-01-16 15:45 ` Rob Herring
2017-01-16 15:52 ` Colin Ian King [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=7cc8f5f0-7899-ca16-2bbb-8869abfda650@canonical.com \
--to=colin.king@canonical.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=nm@ti.com \
--cc=robh@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®