| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Fri, 14 Aug 2015 21:05:35 +0200 From: Uwe Kleine-König <u.kleine-koenig@...gutronix.de> To: Guenter Roeck <linux@...ck-us.net> Cc: linux-watchdog@...r.kernel.org, Wim Van Sebroeck <wim@...ana.be>, linux-kernel@...r.kernel.org, Timo Kokkonen <timo.kokkonen@...code.fi>, linux-doc@...r.kernel.org, Jonathan Corbet <corbet@....net> Subject: Re: [PATCH v2 4/8] watchdog: Make set_timeout function optional Hello Guenter, On Fri, Aug 07, 2015 at 10:02:43PM -0700, Guenter Roeck wrote: > For some watchdogs, the hardware timeout is fixed, and the > watchdog driver depends on the watchdog core to handle the > actual timeout. In this situation, the watchdog driver might > only set the 'timeout' variable but do nothing else. > This can as well be handled by the infrastructure, so make > the set_timeout callback optional. If WDIOF_SETTIMEOUT is > configured but the .set_timeout callback is not available, > update the timeout variable in the infrastructure code. > > Signed-off-by: Guenter Roeck <linux@...ck-us.net> Acked-by: Uwe Kleine-König <u.kleine-koenig@...gutronix.de> Thanks Uwe -- Pengutronix e.K. | Uwe Kleine-König | Industrial Linux Solutions | http://www.pengutronix.de/ | -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists