All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Motherboard Fujitsu D-3076-S
Date: Thu, 08 Aug 2013 11:12:11 +0000	[thread overview]
Message-ID: <52037D0B.1080009@redhat.com> (raw)
In-Reply-To: <52035CE7.3060103@teamnet.de>

Hi,

On 08/08/2013 01:05 PM, Holger Bürger wrote:
> Hi,
>
>> ...
>> ... 2.6.18 is quite old ...
>> ...
>
> I tried to compile this:
>
> "
> make -C /lib/modules/2.6.18-348.el5/build M=/root/test modules
> make[1]: Entering directory `/usr/src/kernels/2.6.18-348.12.1.el5-i686'
>    CC [M]  /root/test/sch56xx-common.o
> /root/test/sch56xx-common.c: In function »sch56xx_device_add«:
> /root/test/sch56xx-common.c:795: Fehler: Implizite Deklaration der
> Funktion »acpi_check_resource_conflict«
> make[2]: *** [/root/test/sch56xx-common.o] Fehler 1
> make[1]: *** [_module_/root/test] Fehler 2
> make[1]: Leaving directory `/usr/src/kernels/2.6.18-348.12.1.el5-i686'
> make: *** [all] Fehler 2
> "
>
> Is there a way to fix this?

Yes you can simply remove the line in question, and the 2 lines remove
it, so remove the following lines:

         err = acpi_check_resource_conflict(&res);
         if (err)
                 goto exit_device_put;

This is not something which I would normally advise, but at the
Fujitsu board in question it is safe to remove the check.

Regards,

Hans

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

  parent reply	other threads:[~2013-08-08 11:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-08  8:55 [lm-sensors] Motherboard Fujitsu D-3076-S Holger Bürger
2013-08-08  9:50 ` Hans de Goede
2013-08-08 11:05 ` Holger Bürger
2013-08-08 11:12 ` Hans de Goede [this message]
2013-08-08 11:24 ` Holger Bürger
2013-08-08 12:32 ` Hans de Goede

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=52037D0B.1080009@redhat.com \
    --to=hdegoede@redhat.com \
    --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.