From: Andrew Morton <akpm@linux-foundation.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: rdunlap@xenotime.net, toralf.foerster@gmx.de,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
jgarzik@pobox.com
Subject: Re: build issue #564 for v2.6.27-rc4 : undefined reference to `NS8390p_init'
Date: Fri, 22 Aug 2008 11:09:02 -0700 [thread overview]
Message-ID: <20080822110902.432dd99e.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080822181234.2f33e993@lxorguk.ukuu.org.uk>
On Fri, 22 Aug 2008 18:12:34 +0100
Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> O> > drivers/built-in.o: In function `wd_probe1':
> > > wd.c:(.init.text+0x2570): undefined reference to `NS8390p_init'
> > > make: *** [.tmp_vmlinux1] Error 1
> >
> > Alan,
> >
> > Do you have any outstanding patches for these wd (and I've seen
> > hp-plus as well IIRC) build issues, or should Jeff have them now?
>
> I'm not really tracking it any more, there were so many patches from so
> many people I couldn't give a definitive answer as to what was applied,
> is queued or is not queued.
>
For the record, and from memory, there were three patches.
One from you which broke my tree.
One from Randy which I merged after several days of you not responding
to our bug reports.
One which I typed in by hand based upon your lackadaisical,
several-month-late English-language description of what I needed to do
to fix it. As we can see, it didn't work.
I wish Jeff hadn't merged the thing after I dropped it - I sat on it
for months waiting in exhasperation for you to actually support your
own work and you never did.
Can we just revert it now?
next prev parent reply other threads:[~2008-08-22 18:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-22 8:33 build issue #564 for v2.6.27-rc4 : undefined reference to `NS8390p_init' Toralf Förster
2008-08-22 17:26 ` Randy.Dunlap
2008-08-22 17:12 ` Alan Cox
2008-08-22 18:09 ` Andrew Morton [this message]
2008-08-22 18:24 ` Alan Cox
2008-08-27 9:19 ` Jeff Garzik
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=20080822110902.432dd99e.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=toralf.foerster@gmx.de \
/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;
as well as URLs for NNTP newsgroup(s).