From: Paul Bame <bame@fc.hp.com>
To: parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] linux-2.4.18-pa19 fpu problem
Date: Wed, 17 Apr 2002 08:42:16 -0600 [thread overview]
Message-ID: <E16xqdU-0001WN-00@paul.bame> (raw)
In-Reply-To: Your message of "Wed, 17 Apr 2002 12:32:11 BST." <20020417123211.L23804@parcelfarce.linux.theplanet.co.uk>
> On Wed, Apr 17, 2002 at 11:02:54AM +0200, joel.soete@freebel.net wrote:
> > Here is some trace I get from the kernel (2.4.18-pa19) make (after a make
> > oldconfig):
> ...
> > I do think that lacks a header to define some function.
>
> this code is crufty old HPUX stuff... the warnings have been there
> basically forever, and nobody's bothered to fix them. Nobody's found a
> problem either :-) If you want to eliminate these warnings by declaring
> everything properly, feel free to send a patch, but I don't think it's
> very important.
Here's the README in the math-emu directory which describes why we
leave the warnings in:
"All files except driver.c are snapshots from the HP-UX kernel. They've
been modified as little as possible. Even though they don't fit the
Linux coding style, please leave them in their funny format just in case
someone in the future, with access to HP-UX source code, is generous
enough to update our copies with later changes from HP-UX -- it'll
make their 'diff' job easier if our code is relatively unmodified.
next prev parent reply other threads:[~2002-04-17 14:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-17 9:02 [parisc-linux] linux-2.4.18-pa19 fpu problem joel.soete
2002-04-17 11:32 ` Matthew Wilcox
2002-04-17 14:42 ` Paul Bame [this message]
2002-04-17 15:44 ` Matthew Wilcox
2002-04-17 17:24 ` joel.soete
2002-04-17 19:41 ` [parisc-linux] gcc-3.2 for parisc James Mcclain
2002-04-18 1:59 ` John David Anglin
2002-04-18 3:48 ` Randolph Chung
2002-04-21 12:43 ` [parisc-linux] linux-2.4.18-pa19 fpu problem Joel Soete
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=E16xqdU-0001WN-00@paul.bame \
--to=bame@fc.hp.com \
--cc=parisc-linux@parisc-linux.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