From: Greg KH <gregkh@linuxfoundation.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
Cc: "tiantao (H)" <tiantao6@huawei.com>,
Tian Tao <tiantao6@hisilicon.com>,
jirislaby@kernel.org, linux-samsung-soc@vger.kernel.org,
linux-serial@vger.kernel.org
Subject: Re: [PATCH] tty: serial: samsung_tty: remove set but not used variables
Date: Mon, 26 Apr 2021 08:56:37 +0200 [thread overview]
Message-ID: <YIZkJUel4RPs4lMf@kroah.com> (raw)
In-Reply-To: <6ea876c3-2ffb-ed39-e927-0eea57af21bd@canonical.com>
On Mon, Apr 26, 2021 at 08:45:44AM +0200, Krzysztof Kozlowski wrote:
> On 23/04/2021 12:14, Greg KH wrote:
> > On Fri, Apr 23, 2021 at 05:54:16PM +0800, tiantao (H) wrote:
> >>
> >> 在 2021/4/23 17:47, Greg KH 写道:
> >>> On Fri, Apr 23, 2021 at 05:39:00PM +0800, Tian Tao wrote:
> >>>> The value of 'ret' is not used, so just delete it.
>
> Tian Tao, please use scripts/get_maintainers.pl to get the list of
> people needed for Cc.
>
> >>>>
> >>>> Signed-off-by: Tian Tao <tiantao6@hisilicon.com>
> >>>> ---
> >>>> drivers/tty/serial/samsung_tty.c | 1 -
> >>>> 1 file changed, 1 deletion(-)
> >>>>
> >>>> diff --git a/drivers/tty/serial/samsung_tty.c b/drivers/tty/serial/samsung_tty.c
> >>>> index d9e4b67..d269d75 100644
> >>>> --- a/drivers/tty/serial/samsung_tty.c
> >>>> +++ b/drivers/tty/serial/samsung_tty.c
> >>>> @@ -2220,7 +2220,6 @@ static int s3c24xx_serial_probe(struct platform_device *pdev)
> >>>> default:
> >>>> dev_warn(&pdev->dev, "unsupported reg-io-width (%d)\n",
> >>>> prop);
> >>>> - ret = -EINVAL;
> >>> That looks odd, shouldn't you do something with this instead of ignoring
> >>> it???
> >>
> >> How about this ?
> >>
> >> diff --git a/drivers/tty/serial/samsung_tty.c
> >> b/drivers/tty/serial/samsung_tty.c
> >> index d9e4b67..9fbc611 100644
> >> --- a/drivers/tty/serial/samsung_tty.c
> >> +++ b/drivers/tty/serial/samsung_tty.c
> >> @@ -2220,8 +2220,7 @@ static int s3c24xx_serial_probe(struct platform_device
> >> *pdev)
> >> default:
> >> dev_warn(&pdev->dev, "unsupported
> >> reg-io-width (%d)\n",
> >> prop);
> >> - ret = -EINVAL;
> >> - break;
> >> + return -EINVAL;
> >>
> >
> > You tell me, does the patch work for you?
> >
> > Is this really a "hard error" and did you now just break devices that
> > used to work properly? Are you correctly unwinding any previously
> > allocated state when you return here?
> >
> > Please do some research on this, and ideally, lots of testing, before
> > submitting it as a real solution.
>
> It's a patch coming from automated tool (e.g. Coverity), so I doubt
> there is any testing here. However the "return -EINVAL" looks correct here:
> 1. No particular unwinding is needed here,
> 2. It's an optional property (not used by existing DTS, only
> non-upstreamed by Samsung) thus treating it as hard-error is fine.
> Probably better to exit than convert it to some default value.
So is that a "Reviwed-by:" or not? :)
next prev parent reply other threads:[~2021-04-26 6:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-23 9:39 [PATCH] tty: serial: samsung_tty: remove set but not used variables Tian Tao
2021-04-23 9:47 ` Greg KH
2021-04-23 9:54 ` tiantao (H)
2021-04-23 10:14 ` Greg KH
2021-04-26 6:45 ` Krzysztof Kozlowski
2021-04-26 6:56 ` Greg KH [this message]
2021-04-26 6:57 ` Krzysztof Kozlowski
2021-04-23 9:55 ` Jiri Slaby
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=YIZkJUel4RPs4lMf@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=tiantao6@hisilicon.com \
--cc=tiantao6@huawei.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;
as well as URLs for NNTP newsgroup(s).