From: Valdis.Kletnieks@vt.edu
To: Alexander Stein <alexander.stein@systec-electronic.com>
Cc: Wim Van Sebroeck <wim@iguana.be>,
linux-kernel@vger.kernel.org,
Samuel Ortiz <sameo@linux.intel.com>,
linux-watchdog@vger.kernel.org
Subject: Re: [PATCH 2/2 v2] Add watchdog driver for Intel E6XX
Date: Tue, 05 Jul 2011 18:24:33 -0400 [thread overview]
Message-ID: <61870.1309904673@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Mon, 04 Jul 2011 15:29:08 +0200." <1309786148-5138-2-git-send-email-alexander.stein@systec-electronic.com>
[-- Attachment #1: Type: text/plain, Size: 501 bytes --]
On Mon, 04 Jul 2011 15:29:08 +0200, Alexander Stein said:
> Signed-off-by: Alexander Stein <alexander.stein@systec-electronic.com>
> +config IE6XX_WATCHDOG
> + tristate "Intel E6XX watchdog"
> + depends on WATCHDOG && PCI && X86
> + select MFD_CORE
> + select LPC_SCH
> + ---help---
> + Hardware driver for the watchdog timer built into the Intel
> + E6XX (TunnelCreek) processor.
That addresses my comment on the patchset, feel free to stick an Acked-By: or
whatever is called for in there...
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2011-07-05 22:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-16 11:05 [PATCH 1/2] Add tunnelcreek watchdog to lpc_sch devices Alexander Stein
2011-06-16 11:05 ` [PATCH 2/2] Add watchdog driver for Intel TunnelCreek Alexander Stein
2011-06-17 21:01 ` Valdis.Kletnieks
2011-06-20 8:51 ` Alexander Stein
2011-07-01 11:00 ` Wim Van Sebroeck
2011-07-04 13:29 ` [PATCH 1/2 v2] Add Intel E6XX watchdog to lpc_sch devices Alexander Stein
2011-07-04 13:29 ` [PATCH 2/2 v2] Add watchdog driver for Intel E6XX Alexander Stein
2011-07-05 22:24 ` Valdis.Kletnieks [this message]
2011-07-22 18:51 ` Wim Van Sebroeck
2011-10-05 8:20 ` [PATCH " Alexander Stein
2011-06-20 14:44 ` [PATCH 1/2] Add tunnelcreek watchdog to lpc_sch devices Samuel Ortiz
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=61870.1309904673@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=alexander.stein@systec-electronic.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=sameo@linux.intel.com \
--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