From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from moutng.kundenserver.de ([212.227.126.171]:62353 "EHLO moutng.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758391Ab1FXNuF (ORCPT ); Fri, 24 Jun 2011 09:50:05 -0400 From: Arnd Bergmann To: Wim Van Sebroeck Subject: Re: [PATCH 8/10 v2] Generic Watchdog Timer Driver Date: Fri, 24 Jun 2011 15:49:32 +0200 Cc: LKML , Linux Watchdog Mailing List , Alan Cox References: <20110618172637.GI3441@infomag.iguana.be> <201106182109.14520.arnd@arndb.de> <20110622200009.GC26745@infomag.iguana.be> In-Reply-To: <20110622200009.GC26745@infomag.iguana.be> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201106241549.32601.arnd@arndb.de> Sender: linux-watchdog-owner@vger.kernel.org List-Id: linux-watchdog@vger.kernel.org On Wednesday 22 June 2011 22:00:09 Wim Van Sebroeck wrote: > prefer to not do that for following reasons: > 1) I deliberately splitted the framework in a series of patches, so that people > understand better what the differen developmentt steps have been historically > and/or logically. By splitting it, I hope that people will understand better > why the API is what it is. > 2) most watchdog drivers don't do this yet. So this teaches existing device > driver writers also that this is a possible feature. > Ok, makes sense. Arnd