The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Guenter Roeck <guenter.roeck@ericsson.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Phil Pokorny <ppokorny@penguincomputing.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"lm-sensors@lm-sensors.org" <lm-sensors@lm-sensors.org>
Subject: Re: [lm-sensors] Location for thermal drivers
Date: Fri, 12 Nov 2010 15:11:55 -0800	[thread overview]
Message-ID: <1289603515.20815.6.camel@groeck-laptop> (raw)
In-Reply-To: <20101112223938.4f2675d7@lxorguk.ukuu.org.uk>

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



  reply	other threads:[~2010-11-12 23:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-12 20:33 Location for thermal drivers Guenter Roeck
2010-11-12 21:53 ` [lm-sensors] " Phil Pokorny
2010-11-12 22:06   ` Guenter Roeck
2010-11-12 22:39     ` Alan Cox
2010-11-12 23:11       ` Guenter Roeck [this message]
2010-11-13  7:21     ` Phil Pokorny
2010-11-13 14:40       ` Guenter Roeck
2010-11-13 17:01         ` Jean Delvare

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=1289603515.20815.6.camel@groeck-laptop \
    --to=guenter.roeck@ericsson.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm-sensors@lm-sensors.org \
    --cc=ppokorny@penguincomputing.com \
    /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