mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Len Brown <lenb@kernel.org>
Cc: Heiko Carstens <heiko.carstens@de.ibm.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Zhang Rui <rui.zhang@intel.com>, Len Brown <len.brown@intel.com>,
	linux-kernel@vger.kernel.org,
	Martin Schwidefsky <schwidefsky@de.ibm.com>,
	Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [PATCH] thermal: fix Kconfig dependencies
Date: Mon, 17 Mar 2008 19:25:03 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.1.00.0803171920320.3020@woody.linux-foundation.org> (raw)
In-Reply-To: <200803171459.10656.lenb@kernel.org>



On Mon, 17 Mar 2008, Len Brown wrote:
> 
> Similarly, ACPI_THERMAL should not depend on THERMAL,
> instead the code that registers with THERMAL should
> simply depend on if THERMAL is selected or not.
> 
> Also, the "default y" should go.
> 
> I'll tinker with this a bit after lunch.

Hmm.. It looks like the same commit that caused these Kconfig issues is 
also the one that causes the problems with lmsensors (I didn't immediately 
realize that it's the exact same commit).

I think that right now the right thing to do is to just revert it, since 
apparently there won't be a released lmsensors version by the time 2.6.25 
gets released that can handle the new sysfs layout, and that we should 
give this some more time to be resolved.

So I'm inclined to revert commit 3152fb9f11cdd2fd8688c2c5cb805e5c09b53dd9 
and plan on revisiting this for 2.6.26. I already got an ack for that from 
Jean Delvare, but I thought I'd mention it in this thread too before I 
actually do the final revert.

Any really strong objections?

		Linus

  reply	other threads:[~2008-03-18  2:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-17  9:58 Heiko Carstens
2008-03-17 16:55 ` Linus Torvalds
2008-03-17 18:43   ` Heiko Carstens
2008-03-17 18:59     ` Len Brown
2008-03-18  2:25       ` Linus Torvalds [this message]
2008-03-18  2:40         ` Zhang, Rui
2008-03-18  5:27           ` Len Brown

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=alpine.LFD.1.00.0803171920320.3020@woody.linux-foundation.org \
    --to=torvalds@linux-foundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=heiko.carstens@de.ibm.com \
    --cc=len.brown@intel.com \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rui.zhang@intel.com \
    --cc=sam@ravnborg.org \
    --cc=schwidefsky@de.ibm.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
all inboxes | Powered by JetHome®