All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@suse.de>
To: Adrian Bunk <bunk@fs.tum.de>, linux-kernel@vger.kernel.org
Cc: bgerst@didntduck.org
Subject: Re: 2.5.14-dj1: misc.o: undefined reference to `__io_virt_debug'
Date: Tue, 7 May 2002 22:57:38 +0200	[thread overview]
Message-ID: <20020507225738.G12134@suse.de> (raw)
In-Reply-To: <20020507205523.D12134@suse.de> <Pine.NEB.4.44.0205072137260.9347-100000@mimas.fachschaften.tu-muenchen.de> <20020507221824.F12134@suse.de>

On Tue, May 07, 2002 at 10:18:25PM +0200, Dave Jones wrote:
 > On Tue, May 07, 2002 at 09:44:41PM +0200, Adrian Bunk wrote:
 > > > I always build my test kernels with CONFIG_DEBUG_IOVIRT=y, and I
 > > > haven't seen this happen.
 > > But you build without CONFIG_MULTIQUAD?
 > Ah, I can reproduce it now. I'll have a poke at it..

Ok, I think this is likely some fall out from Brian's io.h cleanup
from circa 2.5.9.  Brian, anything obvious here ? I took at quick
look at those macros and my brains started leaking out my ears.

-- 
| Dave Jones.        http://www.codemonkey.org.uk
| SuSE Labs

  reply	other threads:[~2002-05-07 20:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-07 18:36 2.5.14-dj1: misc.o: undefined reference to `__io_virt_debug' Adrian Bunk
2002-05-07 18:48 ` Adrian Bunk
2002-05-07 18:55 ` Dave Jones
2002-05-07 19:44   ` Adrian Bunk
2002-05-07 20:18     ` Dave Jones
2002-05-07 20:57       ` Dave Jones [this message]
2002-05-07 22:40     ` Martin J. Bligh
2002-05-07 21:48       ` Brian Gerst
2002-05-07 23:00         ` Martin J. Bligh
2002-05-07 22:43           ` Brian Gerst
2002-05-08  0:12             ` Martin J. Bligh
2002-05-07 21:50       ` Dave Jones
2002-05-07 23:42       ` Martin J. Bligh
2002-05-08  0:14         ` Martin J. Bligh
2002-06-16 11:19           ` Adrian Bunk
2002-06-23 14:45             ` Martin J. Bligh

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=20020507225738.G12134@suse.de \
    --to=davej@suse.de \
    --cc=bgerst@didntduck.org \
    --cc=bunk@fs.tum.de \
    --cc=linux-kernel@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.