From: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
To: <linux-watchdog@vger.kernel.org>, <linux-doc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: Sebastian Reichel <sebastian.reichel@collabora.co.uk>,
<esben.haabendal@gmail.com>,
Alan Cox <gnomes@lxorguk.ukuu.org.uk>,
Guenter Roeck <linux@roeck-us.net>
Subject: Re: [PATCH v6 0/3] watchdog: allow setting deadline for opening /dev/watchdogN
Date: Tue, 6 Jun 2017 10:08:07 +0200 [thread overview]
Message-ID: <cf95ffd6-fb29-bebb-ff54-9f6d648160da@prevas.dk> (raw)
In-Reply-To: <1496134608-7375-1-git-send-email-rasmus.villemoes@prevas.dk>
On 2017-05-30 10:56, Rasmus Villemoes wrote:
>
> v6 tweaks the wording in watchdog-parameters.txt to avoid having to
> update it if and when the watchdog core grows new parameters. It also
> adds a little more rationale to the commit messages for 2/3 and 3/3,
> and adds Reviewed-bys to 1/3 which is unchanged from v5.
Ping. Guenther, is there anything I can do on my end to get this in
before the 4.13 merge window opens? I realize you're busy, but I'd
really appreciate just a brief response to this and the other emails
I've sent the past few weeks.
--
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-06-06 8:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-22 14:06 [PATCH v5 " Rasmus Villemoes
2017-05-22 14:06 ` [PATCH v5 1/3] watchdog: introduce watchdog_worker_should_ping helper Rasmus Villemoes
2017-05-25 0:53 ` Guenter Roeck
2017-05-22 14:06 ` [PATCH v5 2/3] watchdog: introduce watchdog.open_timeout commandline parameter Rasmus Villemoes
2017-05-25 0:56 ` Guenter Roeck
2017-05-30 8:00 ` Rasmus Villemoes
2017-05-22 14:06 ` [PATCH v5 3/3] watchdog: introduce CONFIG_WATCHDOG_OPEN_TIMEOUT Rasmus Villemoes
2017-05-22 18:07 ` [PATCH v5 0/3] watchdog: allow setting deadline for opening /dev/watchdogN Alan Cox
2017-05-22 19:44 ` Guenter Roeck
2017-05-23 7:15 ` Rasmus Villemoes
2017-05-24 14:19 ` Esben Haabendal
2017-05-30 8:56 ` [PATCH v6 " Rasmus Villemoes
2017-05-30 8:56 ` [PATCH v6 1/3] watchdog: introduce watchdog_worker_should_ping helper Rasmus Villemoes
2017-05-30 8:56 ` [PATCH v6 2/3] watchdog: introduce watchdog.open_timeout commandline parameter Rasmus Villemoes
2017-07-08 15:12 ` [v6, " Guenter Roeck
2017-05-30 8:56 ` [PATCH v6 3/3] watchdog: introduce CONFIG_WATCHDOG_OPEN_TIMEOUT Rasmus Villemoes
2017-07-08 15:15 ` [v6,3/3] " Guenter Roeck
2017-07-11 15:50 ` Wim Van Sebroeck
2017-06-06 8:08 ` Rasmus Villemoes [this message]
2017-06-06 13:47 ` [PATCH v6 0/3] watchdog: allow setting deadline for opening /dev/watchdogN Guenter Roeck
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=cf95ffd6-fb29-bebb-ff54-9f6d648160da@prevas.dk \
--to=rasmus.villemoes@prevas.dk \
--cc=esben.haabendal@gmail.com \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=sebastian.reichel@collabora.co.uk \
/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
Powered by JetHome