From: Jack Stone <jwjstone@fastmail.fm>
To: kernel-janitors@vger.kernel.org
Subject: x86 cpumask.h paravirt.h and sparse
Date: Tue, 24 Mar 2009 13:10:18 +0000 [thread overview]
Message-ID: <49C8DBBA.90305@fastmail.fm> (raw)
Hi all,
Running the following commands generates a lot of sparse warnings:
make distclean
make allyesconfig
make C=2
These warnings are mostly symbol '______f' shadows an earlier one.
I couldn't find anything mensioned in the archives for either this list
or lkml.
Are these a known problem and is anyone else working on it?
Thanks,
Jack
next reply other threads:[~2009-03-24 13:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 13:10 Jack Stone [this message]
2009-03-24 13:27 ` x86 cpumask.h paravirt.h and sparse Hannes Eder
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=49C8DBBA.90305@fastmail.fm \
--to=jwjstone@fastmail.fm \
--cc=kernel-janitors@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.