From: Arjan van de Ven <arjanv@redhat.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Arjan van de Ven <arjanv@redhat.com>,
Andi Kleen <ak@colin2.muc.de>, Andrew Morton <akpm@osdl.org>,
Andi Kleen <ak@muc.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Export touch_nmi_watchdog
Date: Tue, 5 Aug 2003 20:31:37 +0000 [thread overview]
Message-ID: <20030805203137.E30256@devserv.devel.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0308051324070.2587-100000@home.osdl.org>; from torvalds@osdl.org on Tue, Aug 05, 2003 at 01:25:09PM -0700
On Tue, Aug 05, 2003 at 01:25:09PM -0700, Linus Torvalds wrote:
>
> On 5 Aug 2003, Arjan van de Ven wrote:
> >
> > having a more generic/portable "trigger_watchdog" function would be
> > better then, such that ALL watchdogs, and not just the NMI one can hook
> > into this
>
> Why are we working around broken drivers?
>
> I say:
> - either fix the driver
> or
> - disable the watchdog entirely.
>
> I don't see any point at all to touch_xxx_watchdog() from a driver.
In principle you are soooo right. Just that it sometimes is HARD to fix
such long delays... I remember working on the qla2x00 driver to fix that ;(
Ok "it's hard" is no excuse.
next prev parent reply other threads:[~2003-08-05 20:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-05 19:29 [PATCH] Export touch_nmi_watchdog Andi Kleen
2003-08-05 19:38 ` Andrew Morton
2003-08-05 20:08 ` Andi Kleen
2003-08-05 20:20 ` Arjan van de Ven
2003-08-05 20:25 ` Linus Torvalds
2003-08-05 20:31 ` Arjan van de Ven [this message]
2003-08-05 21:07 ` Linus Torvalds
2003-08-05 21:05 ` Tim Hockin
2003-08-05 21:14 ` Andi Kleen
2003-08-05 21:15 ` Arjan van de Ven
2003-08-05 21:19 ` Andi Kleen
2003-08-05 22:14 ` Linus Torvalds
2003-08-06 0:07 ` Andi Kleen
2003-08-06 11:06 ` Ingo Oeser
2003-08-06 15:31 ` Linus Torvalds
2003-08-05 20:45 ` Andi Kleen
2003-08-05 21:11 ` Andi Kleen
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=20030805203137.E30256@devserv.devel.redhat.com \
--to=arjanv@redhat.com \
--cc=ak@colin2.muc.de \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.