From: Nishanth Menon <nm@ti.com> To: Colin King <colin.king@canonical.com>, Linus Walleij <linus.walleij@linaro.org>, Lokesh Vutla <lokeshvutla@ti.com>, Tony Lindgren <tony@atomide.com>, linux-gpio@vger.kernel.org Cc: linux-kernel@vger.kernel.org Subject: Re: [PATCH] pinctrl: remove redundant pin < 0 check on unsigned int Date: Fri, 13 Jan 2017 14:41:50 -0600 [thread overview] Message-ID: <081d1a28-9324-7e61-e667-3bd1bc443a04@ti.com> (raw) In-Reply-To: <20170113132039.19830-1-colin.king@canonical.com> On 01/13/2017 07:20 AM, Colin King wrote: > From: Colin Ian King <colin.king@canonical.com> > > pin is an unsigned int and therefore can never be < 0 so > this check is redudant. Remove the check and the associated s/redudant/redundant/ > dev_err error message. > > 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 ------ > 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) { > - dev_err(iod->dev, "invalid pin offset for pin%i\n", pin); > - > - return; > - } > - > pd = &iod->pa[pin]; > cfg = pd->drv_data; > > Thanks. just the $subject could probably be "pinctrl: ti-iodelay:..." Other than these: Acked-by: Nishanth Menon <nm@ti.com> -- Regards, Nishanth Menon
WARNING: multiple messages have this Message-ID (diff)
From: Nishanth Menon <nm@ti.com> To: Colin King <colin.king@canonical.com>, Linus Walleij <linus.walleij@linaro.org>, Lokesh Vutla <lokeshvutla@ti.com>, Tony Lindgren <tony@atomide.com>, <linux-gpio@vger.kernel.org> Cc: <linux-kernel@vger.kernel.org> Subject: Re: [PATCH] pinctrl: remove redundant pin < 0 check on unsigned int Date: Fri, 13 Jan 2017 14:41:50 -0600 [thread overview] Message-ID: <081d1a28-9324-7e61-e667-3bd1bc443a04@ti.com> (raw) In-Reply-To: <20170113132039.19830-1-colin.king@canonical.com> On 01/13/2017 07:20 AM, Colin King wrote: > From: Colin Ian King <colin.king@canonical.com> > > pin is an unsigned int and therefore can never be < 0 so > this check is redudant. Remove the check and the associated s/redudant/redundant/ > dev_err error message. > > 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 ------ > 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) { > - dev_err(iod->dev, "invalid pin offset for pin%i\n", pin); > - > - return; > - } > - > pd = &iod->pa[pin]; > cfg = pd->drv_data; > > Thanks. just the $subject could probably be "pinctrl: ti-iodelay:..." Other than these: Acked-by: Nishanth Menon <nm@ti.com> -- Regards, Nishanth Menon
next prev parent reply other threads:[~2017-01-13 20:42 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-01-13 13:20 [PATCH] pinctrl: remove redundant pin < 0 check on unsigned int Colin King 2017-01-13 20:41 ` Nishanth Menon [this message] 2017-01-13 20:41 ` Nishanth Menon 2017-01-18 9:24 ` 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=081d1a28-9324-7e61-e667-3bd1bc443a04@ti.com \ --to=nm@ti.com \ --cc=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=tony@atomide.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.