From: "Udo A. Steinberg" <reality@delusion.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.5-ac20
Date: Thu, 28 Jun 2001 18:37:54 +0200 [thread overview]
Message-ID: <3B3B5D62.2B84245C@delusion.de> (raw)
In-Reply-To: <20010628164212.A27412@lightning.swansea.linux.org.uk>
Alan Cox wrote:
>
> This is the initial merge with 2.4.6pre - treat this one with care, it may
> not be the most reliable 2.4.5ac release ever made
make[3]: Entering directory `/usr/src/linux-2.4.5-ac/drivers/pnp'
gcc -D__KERNEL__ -I/usr/src/linux-2.4.5-ac/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe
-mpreferred-stack-boundary=2 -march=i686 -malign-functions=4 -DEXPORT_SYMTAB -c pnp_bios.c
pnp_bios.c:252: warning: static declaration for `pnp_bios_dock_station_info' follows non-static
pnp_bios.c:432: warning: no semicolon at end of struct or union
pnp_bios.c:432: parse error before `u16'
pnp_bios.c: In function `pnp_dock_thread':
pnp_bios.c:442: warning: function declaration isn't a prototype
pnp_bios.c:442: warning: extern declaration of `daemonize' doesn't match global one
pnp_bios.c:445: parse error before `struct'
pnp_bios.c:445: warning: unused variable `err'
pnp_bios.c: At top level:
pnp_bios.c:435: storage size of `dock' isn't known
pnp_bios.c:435: warning: `dock' defined but not used
pnp_bios.c:440: warning: `pnp_dock_thread' defined but not used
{standard input}: Assembler messages:
{standard input}:63: Warning: indirect lcall without `*'
{standard input}:143: Warning: indirect lcall without `*'
{standard input}:201: Warning: indirect lcall without `*'
{standard input}:240: Warning: indirect lcall without `*'
next prev parent reply other threads:[~2001-06-28 16:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-28 15:42 Alan Cox
2001-06-28 16:04 ` William Stearns
2001-06-28 16:19 ` William Stearns
2001-06-28 16:37 ` Udo A. Steinberg [this message]
2001-06-28 16:42 ` 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=3B3B5D62.2B84245C@delusion.de \
--to=reality@delusion.de \
--cc=alan@lxorguk.ukuu.org.uk \
--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
all inboxes | Powered by JetHome®