From: "Nithin Nayak Sujir" <nsujir@broadcom.com>
To: "Denys Fedoryshchenko" <denys@visp.net.lb>
Cc: "Michael Chan" <mchan@broadcom.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Latest 3.6.6 are not compiling due tg3 network driver, hwmon_device_unregister
Date: Wed, 14 Nov 2012 19:24:29 -0800 [thread overview]
Message-ID: <50A4606D.4020402@broadcom.com> (raw)
In-Reply-To: <8b566c4a9ee622737212dc17291ee238@visp.net.lb>
This was fixed by
commit de0a41484c47d783dd4d442914815076aa2caac2
Author: Paul Gortmaker <paul.gortmaker@windriver.com>
Date: Mon Oct 1 11:43:49 2012 -0400
tg3: unconditionally select HWMON support when tg3 is enabled.
Nithin.
On 11/14/2012 07:03 PM, Denys Fedoryshchenko wrote:
> Hi
>
> During compiling i am getting that:
>
> drivers/built-in.o: In function `tg3_close':
> tg3.c:(.text+0x12902e): undefined reference to `hwmon_device_unregister'
> drivers/built-in.o: In function `tg3_hwmon_open':
> tg3.c:(.text+0x12ae09): undefined reference to `hwmon_device_register'
>
> Kernel config are at http://nuclearcat.com/config-tg3.txt , but i noticed this error are
> appearing at x86, x64 kernels, probably also other 3.6.x series kernels.
> Disabling TG3 driver helps, but i believe it is not a solution.
>
> ---
> Denys Fedoryshchenko, Network Engineer, Virtual ISP S.A.L.
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2012-11-15 3:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-15 3:03 Latest 3.6.6 are not compiling due tg3 network driver, hwmon_device_unregister Denys Fedoryshchenko
2012-11-15 3:24 ` Nithin Nayak Sujir [this message]
2012-11-15 3:30 ` David Rientjes
2012-11-15 3:43 ` Nithin Nayak Sujir
2012-11-18 22:42 ` David Rientjes
2012-11-19 6:59 ` Denys Fedoryshchenko
2012-11-15 7:22 ` Nithin Sujir
2012-11-15 7:51 ` David Rientjes
2012-11-15 7:56 ` Mathias Krause
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=50A4606D.4020402@broadcom.com \
--to=nsujir@broadcom.com \
--cc=denys@visp.net.lb \
--cc=linux-kernel@vger.kernel.org \
--cc=mchan@broadcom.com \
--cc=netdev@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.