From: Alex Zuepke <azu@sysgo.de>
To: linux-kernel@vger.kernel.org
Subject: (ppc) multiple #include bug
Date: Tue, 23 Oct 2001 12:19:57 +0200 [thread overview]
Message-ID: <3BD5444D.DCD355BB@sysgo.de> (raw)
hi,
i had some compiler errors when playing with the linux trace toolkit
(ltt) and tracked them down:
there is no prevention against multiple #includes in
include/asm-ppc/time.h.
and include/asm-ppc/smplock.h doesn't seem to be safe, too.
i tried kernel 2.4.13.
please add the #ifndef _filename_ \ #define _filename_ \ #endif stuff.
regards,
alex
reply other threads:[~2001-10-23 10:21 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=3BD5444D.DCD355BB@sysgo.de \
--to=azu@sysgo.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