From: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Damien Riegel <damien.riegel@savoirfairelinux.com>,
linux-watchdog@vger.kernel.org, Wim Van Sebroeck <wim@iguana.be>,
kernel@savoirfairelinux.com
Subject: Re: [RFC PATCH 01/13] watchdog: core: add restart handler support
Date: Mon, 2 Nov 2015 21:51:45 -0500 [thread overview]
Message-ID: <20151103025145.GA29120@ketchup.lan> (raw)
In-Reply-To: <56381B03.6030201@roeck-us.net>
Hi Guenter,
On Nov. Monday 02 (45) 06:25 PM, Guenter Roeck wrote:
> On 11/02/2015 05:36 PM, Damien Riegel wrote:
> >Many watchdog drivers implement the same code to register a restart
> >handler. This patch provides a generic way to set such a function.
> >
> >The patch adds a new restart watchdog operation. If a restart priority
> >greater than 0 is needed, the driver can call
> >watchdog_set_restart_priority to set it.
> >
> >Signed-off-by: Damien Riegel <damien.riegel@savoirfairelinux.com>
> >Signed-off-by: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
>
> Makes sense, and good idea. Unless the patch was written by Vivien,
> the second tag should probably be a Reviewed-by: or Acked-by:, though.
We wrote that together, but Damien did most of the work. So I think
Reviewed-by: for me will indeed be most appropriate here.
Also is it OK to include your Reviewed-by: tag in the v1 (given we add
your comments) or not?
Thanks!
-v
next prev parent reply other threads:[~2015-11-03 2:51 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-03 1:36 [RFC PATCH 00/13] watchdog: factorize restart handler registration Damien Riegel
2015-11-03 1:36 ` [RFC PATCH 01/13] watchdog: core: add restart handler support Damien Riegel
2015-11-03 2:25 ` Guenter Roeck
2015-11-03 2:51 ` Vivien Didelot [this message]
2015-11-03 3:14 ` Guenter Roeck
2015-11-03 1:36 ` [RFC PATCH 02/13] watchdog: bcm47xx_wdt: use core restart handler Damien Riegel
2015-11-03 2:26 ` Guenter Roeck
2015-11-03 14:21 ` Vivien Didelot
2015-11-03 14:46 ` Guenter Roeck
2015-11-03 1:36 ` [RFC PATCH 03/13] watchdog: da9063_wdt: " Damien Riegel
2015-11-03 2:26 ` Guenter Roeck
2015-11-03 1:36 ` [RFC PATCH 04/13] watchdog: digicolor_wdt: " Damien Riegel
2015-11-03 2:27 ` Guenter Roeck
2015-11-03 1:36 ` [RFC PATCH 05/13] watchdog: imgpdc_wdt: " Damien Riegel
2015-11-03 2:28 ` Guenter Roeck
2015-11-03 1:36 ` [RFC PATCH 06/13] watchdog: imx2_wdt: " Damien Riegel
2015-11-03 2:29 ` Guenter Roeck
2015-11-03 1:36 ` [RFC PATCH 07/13] watchdog: lpc18xx_wdt: " Damien Riegel
2015-11-03 2:30 ` Guenter Roeck
2015-11-03 1:36 ` [RFC PATCH 08/13] watchdog: meson_wdt: " Damien Riegel
2015-11-03 2:31 ` Guenter Roeck
2015-11-03 1:36 ` [RFC PATCH 09/13] watchdog: moxart_wdt: " Damien Riegel
2015-11-03 2:32 ` Guenter Roeck
2015-11-03 1:36 ` [RFC PATCH 10/13] watchdog: mtk_wdt: " Damien Riegel
2015-11-03 2:35 ` Guenter Roeck
2015-11-03 1:36 ` [RFC PATCH 11/13] watchdog: qcom-wdt: " Damien Riegel
2015-11-03 2:37 ` Guenter Roeck
2015-11-03 1:36 ` [RFC PATCH 12/13] watchdog: s3c2410_wdt: " Damien Riegel
2015-11-03 2:38 ` Guenter Roeck
2015-11-03 1:36 ` [RFC PATCH 13/13] watchdog: sunxi_wdt: " Damien Riegel
2015-11-03 2:41 ` 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=20151103025145.GA29120@ketchup.lan \
--to=vivien.didelot@savoirfairelinux.com \
--cc=damien.riegel@savoirfairelinux.com \
--cc=kernel@savoirfairelinux.com \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--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