From: Dave Jones <davej@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: James Ketrenos <jketreno@linux.intel.com>,
NetDev <netdev@vger.kernel.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
linux-sparse@vger.kernel.org
Subject: Re: warnings in git-wireless
Date: Wed, 6 Jun 2007 21:13:05 -0400 [thread overview]
Message-ID: <20070607011305.GB24941@redhat.com> (raw)
In-Reply-To: <20070606180421.c575f24b.akpm@linux-foundation.org>
On Wed, Jun 06, 2007 at 06:04:21PM -0700, Andrew Morton wrote:
> There _should_ be some #ifdeffable thing which is being passed to cpp when
> we run sparse (but I'm not sure what it is).
#ifdef __CHECKER__
(See include/linux/compiler.h, this is how we implement __user & friends)
Dave
--
http://www.codemonkey.org.uk
prev parent reply other threads:[~2007-06-07 1:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070605020614.3f06b2ab.akpm@linux-foundation.org>
[not found] ` <46671E5D.9070304@linux.intel.com>
[not found] ` <20070606163534.6a6cffb7.akpm@linux-foundation.org>
[not found] ` <4667364A.4040803@linux.intel.com>
2007-06-07 1:04 ` warnings in git-wireless Andrew Morton
2007-06-07 1:13 ` Dave Jones [this message]
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=20070607011305.GB24941@redhat.com \
--to=davej@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=jketreno@linux.intel.com \
--cc=linux-sparse@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).