| 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
| ||
|
Message-ID: <20110323160624.GA8972@suse.de> Date: Wed, 23 Mar 2011 09:06:24 -0700 From: Greg KH <gregkh@...e.de> To: "Weil, Oren jer" <oren.jer.weil@...el.com> Cc: Arnd Bergmann <arnd@...db.de>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "alan@...ux.intel.com" <alan@...ux.intel.com>, "david@...dhou.se" <david@...dhou.se> Subject: Re: [PATCH 0/7] char/mei: Intel MEI Driver On Wed, Mar 23, 2011 at 05:55:47PM +0200, Weil, Oren jer wrote: > >> >I suppose one of the important things to do here is integrate the > >> >watchdog part into the common watchdog infrastructure in > >> >drivers/watchdog. Maybe this driver can export a simple interface to > >> >another module that implements the watchdog device? > >> > >> Yes, this is one the ideas the Alan suggested, we are thinking about > >> this direction in the future. > > > >What's keeping you from doing this now? > > We need to change the driver to expose functions to communicate with the FW > Client (feature) > From other kernel models, the design for now is only from user space. So you need to add support to the watchdog infrastructure for this? For some reason I thought you could kick the watchdog from within kernel code, did I get this wrong? thanks, greg k-h -- 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