From: Paul Mundt <lethal@linux-sh.org>
To: David Engraf <david.engraf@sysgo.com>
Cc: Wim Van Sebroeck <wim@iguana.be>,
linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-sh@vger.kernel.org
Subject: Re: [PATCH] shwdt: fix usage of mod_timer
Date: Thu, 21 Jul 2011 07:53:53 +0000 [thread overview]
Message-ID: <20110721075353.GC27831@linux-sh.org> (raw)
In-Reply-To: <4E26D22B.1040702@sysgo.com>
On Wed, Jul 20, 2011 at 03:03:39PM +0200, David Engraf wrote:
> This patch fixes the usage of mod_timer and makes the driver usable.
> mod_timer must be called with an absolute timeout in jiffies, the old
> implementation used a relative timeout thus the hardware watchdog was
> never triggered.
>
> Signed-off-by: David Engraf <david.engraf@sysgo.com>
>
Applied, thanks.
WARNING: multiple messages have this Message-ID (diff)
From: Paul Mundt <lethal@linux-sh.org>
To: David Engraf <david.engraf@sysgo.com>
Cc: Wim Van Sebroeck <wim@iguana.be>,
linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-sh@vger.kernel.org
Subject: Re: [PATCH] shwdt: fix usage of mod_timer
Date: Thu, 21 Jul 2011 16:53:53 +0900 [thread overview]
Message-ID: <20110721075353.GC27831@linux-sh.org> (raw)
In-Reply-To: <4E26D22B.1040702@sysgo.com>
On Wed, Jul 20, 2011 at 03:03:39PM +0200, David Engraf wrote:
> This patch fixes the usage of mod_timer and makes the driver usable.
> mod_timer must be called with an absolute timeout in jiffies, the old
> implementation used a relative timeout thus the hardware watchdog was
> never triggered.
>
> Signed-off-by: David Engraf <david.engraf@sysgo.com>
>
Applied, thanks.
next prev parent reply other threads:[~2011-07-21 7:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-20 13:03 [PATCH] shwdt: fix usage of mod_timer David Engraf
2011-07-20 13:03 ` David Engraf
2011-07-21 7:53 ` Paul Mundt [this message]
2011-07-21 7:53 ` Paul Mundt
2011-07-22 18:32 ` Wim Van Sebroeck
2011-07-22 18:32 ` 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=20110721075353.GC27831@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=david.engraf@sysgo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@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 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.