From: "[MOc]cda*mirabilos" <mirabilos@netcologne.de>
To: <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.16 Compiler warning
Date: Wed, 28 Nov 2001 22:14:19 -0000 [thread overview]
Message-ID: <00c301c1785a$069803a0$25aefea9@ecce> (raw)
In-Reply-To: <200111282158.WAA02746@harpo.it.uu.se>
> >> This appears to be a non-fatal warning....does this need to be
cleaned up?
> >> [...]
> >> {standard input}: Assembler messages:
> >> {standard input}:1107: Warning: indirect lcall without `*'
> >> {standard input}:1192: Warning: indirect lcall without `*'
IIRC I've had them since 2.0.33 I started dealing with Linux...
next prev parent reply other threads:[~2001-11-28 22:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-28 21:58 2.4.16 Compiler warning Mikael Pettersson
2001-11-28 22:14 ` [MOc]cda*mirabilos [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-28 10:48 Mike Black
2001-11-28 15:19 ` Kai Germaschewski
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='00c301c1785a$069803a0$25aefea9@ecce' \
--to=mirabilos@netcologne.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