From: Justin Cormack <justin@street-vision.com>
To: Wim Van Sebroeck <wim@iguana.be>
Cc: torvalds@osdl.org, Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] 2.6.0-test4 - Watchdog patches
Date: 31 Aug 2003 22:15:09 +0100 [thread overview]
Message-ID: <1062364509.30543.155.camel@lotte.street-vision.com> (raw)
In-Reply-To: <20030831225236.A6938@infomag.infomag.iguana.be>
On Sun, 2003-08-31 at 21:52, Wim Van Sebroeck wrote:
= 0;
>
> /*
> * You must set these - there is no sane way to probe for this board.
> @@ -56,10 +56,17 @@
> * to restart it again.
> */
>
> -#define WDT_START 0x443
> -#define WDT_STOP 0x843
> -
> -static int wd_margin = WD_TIMO;
> +static int wdt_stop = 0x843;
> +module_param(wdt_stop, int, 0);
> +MODULE_PARM_DESC(wdt_stop, "Wafer 5823 WDT 'stop' io port (default 0x843)");
> +
> +static int wdt_start = 0x443;
> +module_param(wdt_start, int, 0);
> +MODULE_PARM_DESC(wdt_start, "Wafer 5823 WDT 'start' io port (default 0x443)");
There is *no point* making these module parameters. There is no other
watchdog that works in exactly the same way but using different io
ports. If there was this still wouldnt be the sensible way to do it.
> + if (timeout < 1 || timeout > 63) {
> + timeout = WD_TIMO;
> + printk (KERN_INFO PFX "timeout value must be 1<=x<=255, using %d\n",
> + timeout);
where did that 63 come from? should be 255.
Also, generally, please cc authors when you send patches. And making the comments the
same in the watchdog drivers is a complete waste of time. If you want to reduce
the amount of duplicated code in the drivers you could make a watchdog_ops interface
for almost all of them.
Justin
next prev parent reply other threads:[~2003-08-31 21:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-31 20:52 Wim Van Sebroeck
2003-08-31 21:15 ` Justin Cormack [this message]
2003-09-03 19:54 ` Wim Van Sebroeck
2003-09-05 0:48 ` Rob Radez
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=1062364509.30543.155.camel@lotte.street-vision.com \
--to=justin@street-vision.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®