From: Dan Carpenter <error27@gmail.com>
To: H Hartley Sweeten <hartleys@visionengravers.com>
Cc: linux-sparse@vger.kernel.org,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: improper sparse warnings in linux kernel build?
Date: Fri, 9 Sep 2011 22:27:19 -0700 [thread overview]
Message-ID: <20110910052719.GC4807@mwanda> (raw)
In-Reply-To: <201109091541.28395.hartleys@visionengravers.com>
On Fri, Sep 09, 2011 at 03:41:28PM -0700, H Hartley Sweeten wrote:
> I'm not really sure what the DEFINE_PER_CPU macro expands to so I'm not
> sure if the 'static' in front is actually getting used or if sparse is just
> confused.
>
> Is this an actual problem in the linux kernel or is sparse just getting
> tripped up by the DEFINE_PER_CPU macro?
>
I don't have a kernel git archive handy, but probably sparse is
correct. Do a "make arch/x86/kernel/cpu/mcheck/mce_intel.i" and run
sparse on the .i file to find the line number that complains.
regards,
dan carpenter
next prev parent reply other threads:[~2011-09-10 5:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-09 22:41 improper sparse warnings in linux kernel build? H Hartley Sweeten
2011-09-09 22:41 ` H Hartley Sweeten
2011-09-10 5:27 ` Dan Carpenter [this message]
2011-09-19 17:49 ` H Hartley Sweeten
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=20110910052719.GC4807@mwanda \
--to=error27@gmail.com \
--cc=hartleys@visionengravers.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sparse@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.