From: Adrian Bunk <bunk@fs.tum.de>
To: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.21-pre1
Date: Wed, 11 Dec 2002 02:14:35 +0100 [thread overview]
Message-ID: <20021211011435.GP17522@fs.tum.de> (raw)
In-Reply-To: <Pine.LNX.4.50L.0212101834240.23096-100000@freak.distro.conectiva>
On Tue, Dec 10, 2002 at 06:37:14PM -0200, Marcelo Tosatti wrote:
> So here goes the first pre of 2.4.21 including the new IDE code merged
> from Alan's tree.
>
> Test it carefully, since the new IDE code is not yet fully tested.
>
> Do not use it with critical data.
>
> Summary of changes from v2.4.20 to v2.4.21-pre1
> ============================================
>...
> Alan Cox <alan@lxorguk.ukuu.org.uk>:
>...
> o ac IDE merge
>...
The ac IDE merge broke the compilation of hd.c (it was already broken in
ac):
<-- snip -->
...
gcc -D__KERNEL__ -I/home/bunk/linux/kernel-2.4/linux-2.4.20/include
-Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing
-fno-common -pipe -mpreferred-stack-boundary=2 -march=k6 -I../
-nostdinc -iwithprefix include -DKBUILD_BASENAME=hd -c -o hd.o hd.c
hd.c:78: conflicting types for `recal_intr'
/home/bunk/linux/kernel-2.4/linux-2.4.20/include/linux/ide.h:1487:
previous declaration of `recal_intr'
hd.c: In function `dump_status':
hd.c:171: `QUEUE_EMPTY' undeclared (first use in this function)
hd.c:171: (Each undeclared identifier is reported only once
hd.c:171: for each function it appears in.)
hd.c:171: `CURRENT' undeclared (first use in this function)
hd.c:169: warning: `devc' might be used uninitialized in this function
hd.c: In function `hd_out':
hd.c:284: `DEVICE_INTR' undeclared (first use in this function)
hd.c:284: `TIMEOUT_VALUE' undeclared (first use in this function)
hd.c: In function `do_reset_hd':
...
make[4]: *** [hd.o] Error 1
make[4]: Leaving directory `/home/bunk/linux/kernel-2.4/linux-2.4.20/drivers/ide/legacy'
<-- snip -->
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2002-12-11 1:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-10 20:37 Linux 2.4.21-pre1 Marcelo Tosatti
2002-12-11 1:14 ` Adrian Bunk [this message]
2002-12-11 8:55 ` Matthias Andree
2002-12-11 9:20 ` Marc-Christian Petersen
2002-12-11 9:08 ` Ralf Hildebrandt
2002-12-11 16:07 ` Alan Cox
2002-12-11 15:34 ` Ralf Hildebrandt
2002-12-11 15:56 ` Ralf Hildebrandt
2002-12-11 17:29 ` Alan Cox
2002-12-15 9:56 ` Ralf Hildebrandt
2002-12-16 6:34 ` Alan Cox
2002-12-17 8:02 ` Ralf Hildebrandt
2002-12-11 9:37 ` Linux 2.4.21-pre1 compile failure: drivers/net/pcmcia/fmvj18x_cs.c Eyal Lebedinsky
2002-12-11 12:51 ` Adrian Bunk
2002-12-11 10:50 ` Linux 2.4.21-pre1 - unresolved symbols: scx200_gpio.o Eyal Lebedinsky
2002-12-12 1:35 ` Linux 2.4.21-pre1 IDE Erik Andersen
2002-12-12 13:10 ` Alan Cox
2002-12-13 14:23 ` Tomas Szepe
2002-12-13 17:42 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2002-12-11 3:58 Linux 2.4.21-pre1 Alex Davis
2002-12-12 15:12 ` Adrian Bunk
2002-12-11 17:51 Petr Vandrovec
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=20021211011435.GP17522@fs.tum.de \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox