From: DervishD <raul@pleyades.net>
To: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: ANSIfy include/linux/a.out.h and include/linux/nls.h
Date: Wed, 15 May 2002 18:06:35 +0200 [thread overview]
Message-ID: <3CE2878B.mailDIB11BDZT@viadomus.com> (raw)
Hello all :))
The GCC compiler insists on ANSIfying the two files mentioned in
the subject, and I think that it should be done by the kernel
maintainers, not GCC ones.
The little patch for 'nls.h' is to add conditional preprocessor
constructs around a typedef:
typedef __u16 wchar_t;
>#ifndef __cplusplus
typedef __u16 wchar_t;
>#endif
The patch for 'a.out.h' is smaller, though:
|#ifdef linux
|#ifdef __linux__
Well, I cannot really see why the ANSI standard is violated in
those two files, but if it is, the changes are pretty small to do...
Raúl
reply other threads:[~2002-05-15 16:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3CE2878B.mailDIB11BDZT@viadomus.com \
--to=raul@pleyades.net \
--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