From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Jeff Garzik <jeff@garzik.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, Ingo Molnar <mingo@elte.hu>,
Atsushi Nemoto <anemo@mba.ocn.ne.jp>,
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 12:25:48 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0807241224040.3283@shark.he.net> (raw)
In-Reply-To: <4888D631.8040401@garzik.org>
On Thu, 24 Jul 2008, Jeff Garzik wrote:
> Alan Cox 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.
>
> My apologies. FWIW, from my point of view the same patch(es) kept getting
> fixed and updated and going around in circles, so I kept waiting. Since it
> was was a net-next issue (until now), I lowered the priority and waited to let
> you guys (you, Andrew, Randy mainly) sort things out.
Randy got frustrated and gave up on this particular issue & patch(es).
This one has gone on far too long...
> So far the only remaining patch I have outstanding and needing to be applied
> is from Atsushi-san via Ingo (message id <20080723104520.GA20672@elte.hu>)...
> is that the last of it?
--
~Randy
next prev parent reply other threads:[~2008-07-24 19:26 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
2008-07-24 19:21 ` Jeff Garzik
2008-07-24 19:25 ` Randy.Dunlap [this message]
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=Pine.LNX.4.64.0807241224040.3283@shark.he.net \
--to=rdunlap@xenotime.net \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=anemo@mba.ocn.ne.jp \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®