From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Wim Van Sebroeck <wim@iguana.be>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] watchdog: ts72xx_wdt: Kill superfluous variable in remove
Date: Tue, 19 Aug 2014 18:14:28 +0300 [thread overview]
Message-ID: <20140819151428.GT1660@lahna.fi.intel.com> (raw)
In-Reply-To: <20140819145916.GC18536@roeck-us.net>
On Tue, Aug 19, 2014 at 07:59:16AM -0700, Guenter Roeck wrote:
> On Tue, Aug 19, 2014 at 02:57:12PM +0300, Mika Westerberg wrote:
> > There is no need to store the return value of misc_deregister() in a
> > variable. Instead we can just return the value directly.
> >
> > Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
> > ---
> > drivers/watchdog/ts72xx_wdt.c | 6 +-----
> > 1 file changed, 1 insertion(+), 5 deletions(-)
> >
> > diff --git a/drivers/watchdog/ts72xx_wdt.c b/drivers/watchdog/ts72xx_wdt.c
> > index afa9d6ef353a..dee9c6cbe6df 100644
> > --- a/drivers/watchdog/ts72xx_wdt.c
> > +++ b/drivers/watchdog/ts72xx_wdt.c
> > @@ -428,11 +428,7 @@ static int ts72xx_wdt_probe(struct platform_device *pdev)
> >
> > static int ts72xx_wdt_remove(struct platform_device *pdev)
> > {
> > - int error;
> > -
> > - error = misc_deregister(&ts72xx_wdt_miscdev);
> > -
> > - return error;
> > + return misc_deregister(&ts72xx_wdt_miscdev);
>
> Is that worth it, and does it even reduce code size ?
Well, it makes that particular function look better.
> Converting the driver to use the watchdog infrastructure would make much more sense
> (if someone can test the result).
I agree that converting makes sense, but that is subject of a separate patch.
next prev parent reply other threads:[~2014-08-19 15:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-19 11:57 Mika Westerberg
2014-08-19 14:59 ` Guenter Roeck
2014-08-19 15:14 ` Mika Westerberg [this message]
2014-08-21 18:47 ` Guenter Roeck
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=20140819151428.GT1660@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=wim@iguana.be \
/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
Powered by JetHome