linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Muhammad Falak R Wani <falakreyaz@gmail.com>
Cc: Wim Van Sebroeck <wim@iguana.be>,
	linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] watchdog: cpwd: Use setup_timer()
Date: Tue, 10 May 2016 14:51:57 -0700	[thread overview]
Message-ID: <20160510215157.GA19128@roeck-us.net> (raw)
In-Reply-To: <1462539581-26207-1-git-send-email-falakreyaz@gmail.com>

On Fri, May 06, 2016 at 06:29:40PM +0530, Muhammad Falak R Wani wrote:
> The function setup_timer combines the initialization of a timer with
> the initialization of the timer's function and data fields.
> The multiline code for timer initialization is now replaced
> with function setup_timer.
> 
> Signed-off-by: Muhammad Falak R Wani <falakreyaz@gmail.com>

Reviewed-by: Guenter Roeck <linux@roeck-us.net>

> ---
>  drivers/watchdog/cpwd.c | 4 +---
>  1 file changed, 1 insertion(+), 3 deletions(-)
> 
> diff --git a/drivers/watchdog/cpwd.c b/drivers/watchdog/cpwd.c
> index 0200768..71ee079 100644
> --- a/drivers/watchdog/cpwd.c
> +++ b/drivers/watchdog/cpwd.c
> @@ -611,9 +611,7 @@ static int cpwd_probe(struct platform_device *op)
>  	}
>  
>  	if (p->broken) {
> -		init_timer(&cpwd_timer);
> -		cpwd_timer.function	= cpwd_brokentimer;
> -		cpwd_timer.data		= (unsigned long) p;
> +		setup_timer(&cpwd_timer, cpwd_brokentimer, (unsigned long)p);
>  		cpwd_timer.expires	= WD_BTIMEOUT;
>  
>  		pr_info("PLD defect workaround enabled for model %s\n",
> -- 
> 1.9.1
> 

  parent reply	other threads:[~2016-05-10 21:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-06 12:59 [PATCH 1/2] watchdog: cpwd: Use setup_timer() Muhammad Falak R Wani
2016-05-06 12:59 ` [PATCH 2/2] watchdog: shwdt: " Muhammad Falak R Wani
2016-05-10 21:52   ` Guenter Roeck
2016-05-14 18:34   ` Wim Van Sebroeck
2016-05-10 21:51 ` Guenter Roeck [this message]
2016-05-14 18:34 ` [PATCH 1/2] watchdog: cpwd: " Wim Van Sebroeck

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=20160510215157.GA19128@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=falakreyaz@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).