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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 12 Nov 2010 15:11:55 -0800
From:	Guenter Roeck <guenter.roeck@...csson.com>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
CC:	Phil Pokorny <ppokorny@...guincomputing.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"lm-sensors@...sensors.org" <lm-sensors@...sensors.org>
Subject: Re: [lm-sensors] Location for thermal drivers

On Fri, 2010-11-12 at 17:39 -0500, Alan Cox wrote:
> > > Why does drivers/thermal exist if there are no drivers in it and no maintainer?
> 
> It has a maintainer - they are just not listed in MAINTAINERS only in the
> file itself.
> 
> > > 
> > The framework resides there. Drivers supporting it are in various
> > platform directories.
> > 
> > As for why there are no drivers - only the framework - in
> > drivers/thermal, and why there is no maintainer - no idea.
> 
> Well I could put it in arch/x86/platform/mrst now we have that structure
> from 2.6.37-rc1 onwards

I thought the driver is for Medfield ? Is that the same ? Or do you mean
you would add platform/medfield ? That might be another option.

Then there is drivers/platform/x86/intel_menlow.c, which has the thermal
driver code for Menlow.

Guenter


--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ