public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Denis Turischev <denis@compulab.co.il>
To: Wim Van Sebroeck <wim@iguana.be>
Cc: Mike Rapoport <mike@compulab.co.il>,
	Joe Perches <joe@perches.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Andrey Panin <pazke@centrinvest.ru>,
	akpm@linux-foundation.org
Subject: Re: [PATCH v2] add SBC-FITPC2 watchdog driver
Date: Thu, 06 Aug 2009 11:34:17 +0300	[thread overview]
Message-ID: <4A7A9589.1090106@compulab.co.il> (raw)
In-Reply-To: <20090804153331.GA30892@infomag.iguana.be>

Thanks Wim,

Tested, seems ok.

Denis

Wim Van Sebroeck wrote:
> Hi Mike, Denis,
>
>   
>>> From: Denis Turischev <denis@compulab.co.il>
>>>       
>> This patch adds support for watchdog found on SBC-FITPC2 board.
>>
>> --
>> v2 changes:
>> - reorder fitpc2_wdt_write to reduce the indent
>> - change printk levels
>> - use pr_fmt
>> - add release_region in the _init error path
>>
>> Signed-off-by: Denis Turischev <denis@compulab.co.il>
>> Signed-off-by: Mike Rapoport <mike@compulab.co.il>
>>     
>
> Some remarks:
> 1) If you dou request_regions in the init section then you need to do release_regions also in the exit section.
> 2) we prefer:
>  static long wdt_ioctl(parameters
> 			rest_of_parameters)
> instead of
>  static long
>  wdt_ioctl(parameters)
> 3) misc_deregister can return with an error. If it does you need to do the release_regions also.
> 4) as Andrew allready pointed out spinlock needs to be initialized.
> 5) if you don't use the reboot_notifier then you don't need to include linux/notifier.h and linux/reboot.h .
>
> I adapted the code.
> Can you test the attached diff?
>
> Thanks in advance,
> Wim.
>
>   


      reply	other threads:[~2009-08-06  8:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-21 10:13 [PATCH v2] add SBC-FITPC2 watchdog driver Mike Rapoport
2009-07-27 21:10 ` Andrew Morton
2009-08-04 15:33 ` Wim Van Sebroeck
2009-08-06  8:34   ` Denis Turischev [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=4A7A9589.1090106@compulab.co.il \
    --to=denis@compulab.co.il \
    --cc=akpm@linux-foundation.org \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mike@compulab.co.il \
    --cc=pazke@centrinvest.ru \
    --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