From: Neil Booth <neil@daikokuya.demon.co.uk>
To: richbaum@acm.org
Cc: linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linus Torvalds <torvalds@transmeta.com>
Subject: Re: [PATCH] Fix compile warnings in 2.4.0
Date: Sun, 7 Jan 2001 22:21:37 +0000 [thread overview]
Message-ID: <20010107222137.B14699@daikokuya.demon.co.uk> (raw)
In-Reply-To: <3A589726.5449.291B75@localhost>
In-Reply-To: <3A589726.5449.291B75@localhost>; from baumr1@coral.indstate.edu on Sun, Jan 07, 2001 at 04:19:50PM -0500
Rich Baum wrote:-
> This patch should fix the rest of the warnings about #endif
> statements when using the 20001225 gcc snapshot. Thanks to
> Keith Owens for providing a script to automate this process. It got
> the job done sooner and found warnings to fix for non x86 platforms.
Unfortunately, the script also gets stuff it shouldn't, and in some
cases adds comments within the comments, probably causing stuff to
stop compiling altogether. Some examples below.
Neil.
> +# endif /* # */
[....]
> * appropriate for an 030 or an 040. This is useful for debugging purposes
> - * and as such is enclosed in #ifdef MMU_PRINT/#endif clauses.
> + * and as such is enclosed in #ifdef MMU_PRINT/#endif /* clauses. */
> *
[...]
> * is specifically for debugging and can be very useful. It is surrounded by
> - * #ifdef CONSOLE/#endif clauses so it doesn't have to ship in known-good
> + * #ifdef CONSOLE/#endif /* clauses so it doesn't have to ship in known-good */
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-07 22:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-07 21:19 Rich Baum
2001-01-07 22:21 ` Neil Booth [this message]
2001-01-08 0:52 ` Keith Owens
2001-01-08 12:38 ` Rich Baum
-- strict thread matches above, loose matches on Subject: below --
2001-01-06 13:54 Rich Baum
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=20010107222137.B14699@daikokuya.demon.co.uk \
--to=neil@daikokuya.demon.co.uk \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=richbaum@acm.org \
--cc=torvalds@transmeta.com \
/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®