mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Wim Van Sebroeck <wim@iguana.be>,
	LKML <linux-kernel@vger.kernel.org>,
	Linux Watchdog Mailing List <linux-watchdog@vger.kernel.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH 1/10 v2] Generic Watchdog Timer Driver
Date: Sun, 19 Jun 2011 20:44:00 -0700	[thread overview]
Message-ID: <20110619204400.d732e8aa.rdunlap@xenotime.net> (raw)
In-Reply-To: <201106182058.14702.arnd@arndb.de>

On Sat, 18 Jun 2011 20:58:14 +0200 Arnd Bergmann wrote:

> On Saturday 18 June 2011 19:19:46 Wim Van Sebroeck wrote:
> > watchdog: WatchDog Timer Driver Core - Part 1
> > 
> > The WatchDog Timer Driver Core is a framework
> > that contains the common code for all watchdog-driver's.
> > It also introduces a watchdog device structure and the
> > operations that go with it.
> > 
> > This is the introduction of this framework. This part
> > supports the minimal watchdog userspace API (or with
> > other words: the functionality to use /dev/watchdog's
> > open, release and write functionality as defined in
> > the simplest watchdog API). Extra functionality will
> > follow in the next set of patches.
> > 
> > Signed-off-by: Alan Cox <alan@lxorguk.ukuu.org.uk>
> > Signed-off-by: Wim Van Sebroeck <wim@iguana.be>
> 
> Hi Wim,
> 
> Great to see the series posted again, I'm looking forward to seeing
> this included in 3.1.
> 
> I've got a few comments for stuff that can still be improved.
> 
> I noticed that your email subject lines are all the same, you should
> probably see if you mail setup can be fixed to take the one-line
> comment in each patch as the subject, and also to make all mails
> replies to the [PATCH 0/10] email.

It would also be good to include diffstat summaries with each patch.

This info in Documentation/ioctl/ioctl-number.txt does not change, correct?

'W'	00-1F	linux/watchdog.h	conflict!

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

  reply	other threads:[~2011-06-20  3:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-18 17:19 Wim Van Sebroeck
2011-06-18 18:58 ` Arnd Bergmann
2011-06-20  3:44   ` Randy Dunlap [this message]
2011-06-22 20:15     ` Wim Van Sebroeck
2011-06-22 12:24   ` Mark Brown
2011-06-22 19:50   ` Wim Van Sebroeck
2011-06-24 13:59     ` Arnd Bergmann
2011-06-24 19:27       ` Wim Van Sebroeck
2011-07-06 19:17   ` Wim Van Sebroeck
2011-07-06 19:26     ` Alan Cox
2011-07-06 19:30     ` Wolfram Sang
2011-06-22 18:28 ` Chris Friesen
2011-06-22 20:25   ` Wim Van Sebroeck

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=20110619204400.d732e8aa.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®