All of lore.kernel.org
 help / color / mirror / Atom feed
From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] nvidia nforce410 chipset / ASUS K8N-VM
Date: Fri, 30 Jun 2006 11:16:56 +0000	[thread overview]
Message-ID: <20060630131656.1cc538b9.khali@linux-fr.org> (raw)
In-Reply-To: <44A326F3.3070300@winbond.com>

Hi Yuan, Daan,

> Daan Willems wrote:
> > I've tried the patch on a plain 2.6.17.1 vanilla kernel, but using the 
> > newbuilt module still doesn't show me the voltages. However on building 
> > the module with the patch applied I get the following message:
> > 
> > WARNING: drivers/acpi/processor.o - Section mismatch: reference to 
> > .init.data: from .text between 'acpi_processor_power_init' (at offset 
> > 0xf2f) and 'acpi_processor_cst_has_changed'
> 
> One possible reason is you need to install new lm_sensors2 user space tools.
> If it is not this reason, i can not help you more :(
> I still have no chance to try 2.6.17.1 kernel...

No, this is a completely unrelated warning. There's something wrong in
the acpi code, the compiler warns about it since 2.6.17 (it was already
wrong before, but the compiler wasn't taught to detect the mistake
until recently.

So, Daan, you can ignore that warning safely. You would have the same
warning without the patch. I have the warning too for quite some times
now and nothing bad happened ;) Let's just hope the acpi people
eventually show up and fix it, so that people stop being frightened!

-- 
Jean Delvare


      parent reply	other threads:[~2006-06-30 11:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-29  1:03 [lm-sensors] nvidia nforce410 chipset / ASUS K8N-VM Yuan Mu
2006-06-29  7:33 ` Daan Willems
2006-06-29  7:46 ` Yuan Mu
2006-06-29 18:05 ` Daan Willems
2006-06-30  0:59 ` Yuan Mu
2006-06-30  6:20 ` Daan Willems
2006-06-30 10:49 ` Yuan Mu
2006-06-30 11:16 ` Jean Delvare [this message]

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=20060630131656.1cc538b9.khali@linux-fr.org \
    --to=khali@linux-fr.org \
    --cc=lm-sensors@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.