From: Andreas Schwab <schwab@suse.de>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-kbuild <linux-kbuild@vger.kernel.org>,
janitors <kernel-janitors@vger.kernel.org>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: Many warnings from our userspace headers
Date: Tue, 30 Dec 2008 11:43:22 +0100 [thread overview]
Message-ID: <jeiqp2j645.fsf@sykes.suse.de> (raw)
In-Reply-To: <20081230103348.GA363@uranus.ravnborg.org> (Sam Ravnborg's message of "Tue, 30 Dec 2008 11:33:48 +0100")
Sam Ravnborg <sam@ravnborg.org> writes:
> /home/sam/kernel/knext.git/usr/include/linux/acct.h:62: leaks CONFIG_M68K to userspace where it is not valid
IMHO this is a false positive, since it is protected by __KERNEL__ in
the same expression.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2008-12-30 10:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-30 10:33 Many warnings from our userspace headers Sam Ravnborg
2008-12-30 10:43 ` Andreas Schwab [this message]
2008-12-30 12:07 ` Sam Ravnborg
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=jeiqp2j645.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=dwmw2@infradead.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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