From: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Wim Van Sebroeck <wim@iguana.be>,
Jonathan Corbet <corbet@lwn.net>,
Sylvain Lemieux <slemieux.tyco@gmail.com>,
<linux-watchdog@vger.kernel.org>, <linux-doc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 2/3] watchdog: introduce watchdog.open_timeout commandline parameter
Date: Mon, 30 Jan 2017 11:33:08 +0100 [thread overview]
Message-ID: <993bd1ec-5c63-7e6f-bb80-5f37e7d1ab59@prevas.dk> (raw)
In-Reply-To: <7d6b0bb9-43ec-d600-607a-0b43dea39f24@prevas.dk>
On 2017-01-13 10:11, Rasmus Villemoes wrote:
> On 2017-01-11 12:02, Guenter Roeck wrote:
>> This will require input from others on the semantics.
>
> I agree, it would be nice to have others chime in on whether they'd even
> find this useful, and what semantics they'd like.
Ping.
--
Rasmus Villemoes
Software Developer
Prevas A/S
Hedeager 1
DK-8200 Aarhus N
+45 51210274
rasmus.villemoes@prevas.dk
www.prevas.dk
next prev parent reply other threads:[~2017-01-30 10:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-09 15:02 [PATCH v4 0/3] watchdog: allow setting deadline for opening /dev/watchdogN Rasmus Villemoes
2017-01-09 15:02 ` [PATCH v4 1/3] watchdog: introduce watchdog_worker_should_ping helper Rasmus Villemoes
2017-01-09 15:02 ` [PATCH v4 2/3] watchdog: introduce watchdog.open_timeout commandline parameter Rasmus Villemoes
2017-01-10 18:08 ` Guenter Roeck
2017-01-11 8:11 ` Rasmus Villemoes
2017-01-11 11:02 ` Guenter Roeck
2017-01-13 9:11 ` Rasmus Villemoes
2017-01-30 10:33 ` Rasmus Villemoes [this message]
2017-01-09 15:02 ` [PATCH v4 3/3] watchdog: introduce CONFIG_WATCHDOG_OPEN_TIMEOUT Rasmus Villemoes
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=993bd1ec-5c63-7e6f-bb80-5f37e7d1ab59@prevas.dk \
--to=rasmus.villemoes@prevas.dk \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=slemieux.tyco@gmail.com \
--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®