From: Alan Cox <alan@redhat.com>
To: bunk@fs.tum.de (Adrian Bunk)
Cc: vanonim@bluewin.ch (Mario Vanoni), alan@redhat.com (Alan Cox),
andre@linux-ide.org (Andre Hedrick),
linux-kernel@vger.kernel.org (linux-kernel@vger.kernel.org)
Subject: Re: 2.4-pre5[{-}xyz]: 4 machines, feedback only
Date: Mon, 9 Sep 2002 16:51:31 -0400 (EDT) [thread overview]
Message-ID: <200209092051.g89KpVg05996@devserv.devel.redhat.com> (raw)
In-Reply-To: <Pine.NEB.4.44.0209092234120.11139-100000@mimas.fachschaften.tu-muenchen.de> from "Adrian Bunk" at Sep 09, 2002 10:41:16 PM
> ide-proc.c is compiled into idedriver.o even if no IDE support is compiled
> into the kernel. That isn't new. The problem that causes these undefined
Thts fine
> references is that in -ac4 some functions that use functions from other
> ide files (which aren't compiled when building a kernel without IDE
> support) are no longer static (because they are now exported to modules).
idedriver.o shouldnt be getting into a kernel without IDE. Thats the
real problem
prev parent reply other threads:[~2002-09-09 20:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-08 19:48 2.4-pre5[{-}xyz]: 4 machines, feedback only Mario Vanoni
2002-09-08 20:34 ` Adrian Bunk
2002-09-09 20:41 ` Adrian Bunk
2002-09-09 20:51 ` Alan Cox [this message]
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=200209092051.g89KpVg05996@devserv.devel.redhat.com \
--to=alan@redhat.com \
--cc=andre@linux-ide.org \
--cc=bunk@fs.tum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=vanonim@bluewin.ch \
/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