linux-kernel - Re: [PATCH 2/2] Add watchdog driver for Intel TunnelCreek

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

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 20 Jun 2011 10:51:48 +0200
From:	Alexander Stein <alexander.stein@...tec-electronic.com>
To:	Valdis.Kletnieks@...edu
Cc:	linux-kernel@...r.kernel.org, Samuel Ortiz <sameo@...ux.intel.com>,
	Wim Van Sebroeck <wim@...ana.be>,
	linux-watchdog@...r.kernel.org
Subject: Re: [PATCH 2/2] Add watchdog driver for Intel TunnelCreek

On Friday 17 June 2011 23:01:15 Valdis.Kletnieks@...edu wrote:
> On Thu, 16 Jun 2011 13:05:50 +0200, Alexander Stein said:
> > +config INTEL_TUNNELCREEK_WATCHDOG
> > +	tristate "Intel TunnelCreek watchdog"
> > +	depends on WATCHDOG && PCI && X86
> > +	select MFD_CORE
> > +	select LPC_SCH
> > +	---help---
> > +	  Hardware driver for the watchdog timer built into the Intel
> > +	  Tunnel Creek processor.
> 
> Please add part names here so we don't have to guess/remember what the
> now-retired code name for a processor was.  Just because the guy who wrote
> the driver knows what the development name was doesn't mean that the poor
> guy saying 'make oldconfig' knows whether this is a driver he cares about.
> 
> http://www.engadget.com/2010/09/15/intel-retires-tunnel-creek-codename-debu
> ts-e600-series-atom-sys/

Thanks for the hint.
Would you also recommend to rename the driver module name? Currently it is 
intel_tunnelcreek_watchdog, so it may be called intel_e6xx_watchdog.

Regards,
Alexander
--
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/