public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: Sebastian Pigulak <dreamin@interia.pl>,
	linux-kernel@vger.kernel.org, Sebastian Witt <se.witt@gmx.net>,
	Greg KH <greg@kroah.com>,
	lm-sensors@lm-sensors.org
Subject: Re: [2.6 patch] SENSORS_ATXP1 must select I2C_SENSOR
Date: Fri, 1 Jul 2005 16:41:08 +0200	[thread overview]
Message-ID: <20050701164108.0bc4e364.khali@linux-fr.org> (raw)
In-Reply-To: <20050630221727.GE27478@stusta.de>

Hi Adrian,

> > I've tried patching linux-2.6.13-RC1 with patch-2.6.13-rc1-git2 and
> > building atxp1(it allows Vcore voltage changing) into the kernel.
> > Unfortunately, the kernel compilation stops with:
> > 
> > LD      init/built-in.o
> > LD      vmlinux
> > drivers/built-in.o(.text+0x92298): In function `atxp1_detect':
> > : undefined reference to `i2c_which_vrm'
> > drivers/built-in.o(.text+0x921ae): In function
> > `atxp1_attach_adapter': : undefined reference to `i2c_detect'
> > make: *** [vmlinux] B??d 1
> > ==> ERROR: Build Failed.  Aborting... 
> > 
> > Could someone have a look at the module and possibly fix it up?
> 
> The patch below should fix it.

Good catch. However, this fix will conflict with a larger patch I am
working on (moving hardware monitoring drivers to a different directory
[1]), so I applied a different fix on top of my own stack, and will send
all this stuff to Greg as soon as possible.

[1] http://lkml.org/lkml/2005/6/27/302

Thanks,
-- 
Jean Delvare

  parent reply	other threads:[~2005-07-01 14:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-30 21:47 atxp1 module not compiling Sebastian Pigulak
2005-06-30 22:17 ` [2.6 patch] SENSORS_ATXP1 must select I2C_SENSOR Adrian Bunk
2005-06-30 23:01   ` Sebastian Pigulak
2005-07-01 14:41   ` Jean Delvare [this message]
2005-06-30 22:23 ` [PATCH]Re: atxp1 module not compiling; needs I2C_SENSOR Prakash Punnoor

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=20050701164108.0bc4e364.khali@linux-fr.org \
    --to=khali@linux-fr.org \
    --cc=bunk@stusta.de \
    --cc=dreamin@interia.pl \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm-sensors@lm-sensors.org \
    --cc=se.witt@gmx.net \
    /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