From: Christoph Hellwig <hch@infradead.org>
To: Javier Marcet <jmarcet@pobox.com>
Cc: Alan Cox <alan@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.20-pre2-ac1
Date: Wed, 14 Aug 2002 19:03:14 +0100 [thread overview]
Message-ID: <20020814190313.A22068@infradead.org> (raw)
In-Reply-To: <20020814175455.GA5254@jerry.boludo.cjb.net>; from jmarcet@pobox.com on Wed, Aug 14, 2002 at 07:54:55PM +0200
On Wed, Aug 14, 2002 at 07:54:55PM +0200, Javier Marcet wrote:
> gcc -D__KERNEL__ -I/usr/src/linux-2.4.20-pre2-ac1/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=athlon-xp -nostdinc -I /usr/lib/gcc-lib/i686-pc-linux-gnu/3.2/include -DKBUILD_BASENAME=check -DEXPORT_SYMTAB -c check.c
> check.c: In function `devfs_register_disc':
> check.c:328: structure has no member named `number'
> check.c:329: structure has no member named `number'
> check.c: In function `devfs_register_partitions':
> check.c:361: structure has no member named `number'
This is also present in plain 2.4.20-pre2 and I sent the fix to Marcelo and
this list a few hours before -pre2 was released.
next prev parent reply other threads:[~2002-08-14 17:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-14 16:34 Linux 2.4.20-pre2-ac1 Alan Cox
2002-08-14 16:44 ` Christoph Hellwig
2002-08-14 16:46 ` Alan Cox
2002-08-14 17:42 ` Steven Cole
2002-08-14 20:29 ` Greg Louis
2002-08-14 21:06 ` Steven Cole
2002-08-15 0:07 ` Alan Cox
2002-08-14 17:54 ` Javier Marcet
2002-08-14 18:03 ` Christoph Hellwig [this message]
2002-08-14 19:44 ` Unresolved symbols in nfsd in 2.4.20-pre2-ac1 Samuel Flory
2002-08-14 22:11 ` Linux 2.4.20-pre2-ac1 Adrian Bunk
2002-08-14 22:47 ` Adrian Bunk
2002-08-14 23:56 ` Chad Young
2002-08-15 1:03 ` Eyal Lebedinsky
2002-08-15 1:14 ` Alan Cox
2002-08-15 2:30 ` Kai Germaschewski
2002-08-15 10:52 ` 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=20020814190313.A22068@infradead.org \
--to=hch@infradead.org \
--cc=alan@redhat.com \
--cc=jmarcet@pobox.com \
--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.