All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Jeff Garzik <jeff@garzik.org>,
	Atsushi Nemoto <anemo@mba.ocn.ne.jp>,
	jgarzik@redhat.com, akpm@linux-foundation.org,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [build failure] hp-plus.c: (.text+0xd7c1a): undefined reference to `ei_close'
Date: Thu, 24 Jul 2008 11:29:20 +0200	[thread overview]
Message-ID: <20080724092920.GC31358@elte.hu> (raw)
In-Reply-To: <20080724100615.764bac36@lxorguk.ukuu.org.uk>


* Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:

> On Thu, 24 Jul 2008 07:26:03 +0200
> Ingo Molnar <mingo@elte.hu> wrote:
> 
> > 
> > not sure it's known but despite all the fixes i still get:
> 
> I'll have a look at this next week or possibly the week after. The 
> original patches worked but they spent 3 months going round in circles 
> and I've completely given up even trying to work out what happened or 
> why all the previous updates I sent were ignored.

ok - meanwhile i'm using the workaround hack below.

	Ingo

--------------------->
commit 91de2dc9031b92157f067d78aaf2c8e58a965c0d
Author: Ingo Molnar <mingo@elte.hu>
Date:   Mon Jul 21 21:18:29 2008 +0200

    hp-plus.c: work around build failure
    
    Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
 drivers/net/Kconfig |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/drivers/net/Kconfig b/drivers/net/Kconfig
index fa533c2..1c809e4 100644
--- a/drivers/net/Kconfig
+++ b/drivers/net/Kconfig
@@ -1129,6 +1129,8 @@ config EEXPRESS_PRO
 config HPLAN_PLUS
 	tristate "HP PCLAN+ (27247B and 27252A) support"
 	depends on NET_ISA
+	# broken build with config-Mon_Jul_21_20_21_08_CEST_2008.bad
+	depends on 0
 	select CRC32
 	help
 	  If you have a network (Ethernet) card of this type, say Y and read

  reply	other threads:[~2008-07-24  9:30 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-21 14:35 [PATCH] 8390: Fix ne.c build Atsushi Nemoto
2008-07-21 19:15 ` [build failure] hp-plus.c: (.text+0xd7c1a): undefined reference to `ei_close' Ingo Molnar
2008-07-21 20:42   ` Alan Cox
2008-07-22  7:23     ` Ingo Molnar
2008-07-22 10:28       ` Alan Cox
2008-07-22 22:00       ` Jeff Garzik
2008-07-23 10:45         ` Ingo Molnar
2008-07-24  5:26           ` Ingo Molnar
2008-07-24  9:06             ` Alan Cox
2008-07-24  9:29               ` Ingo Molnar [this message]
2008-07-24 19:21               ` Jeff Garzik
2008-07-24 19:25                 ` Randy.Dunlap
2008-07-24 19:54                 ` Alan Cox
2008-07-25 17:09             ` Alan Cox
2008-07-25 18:03               ` [PATCH] hugetlb: fix CONFIG_SYSCTL=n build Nishanth Aravamudan
2008-07-25 20:33               ` [PATCH RESEND] " Nishanth Aravamudan
2008-07-25 21:29                 ` Andrew Morton
2008-07-25 21:52                   ` Nishanth Aravamudan
2008-07-26  0:32                 ` Linus Torvalds
2008-07-26  0:44                   ` Andrew Morton
2008-07-26  1:25                     ` Nishanth Aravamudan
2008-07-26  1:52                       ` Andrew Morton
2008-07-22 12:24 ` [PATCH] 8390: Fix ne.c build Alan Cox

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=20080724092920.GC31358@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=anemo@mba.ocn.ne.jp \
    --cc=jeff@garzik.org \
    --cc=jgarzik@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --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.