From: Dan Carpenter <dan.carpenter@oracle.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [infiniband:for-next 13/14] drivers/infiniband/hw/qib/qib_keys.c:64:23: sparse: incompatible typ
Date: Fri, 06 Jul 2012 12:23:54 +0000 [thread overview]
Message-ID: <20120706122354.GB8027@mwanda> (raw)
In-Reply-To: <20120706080229.GB28650@localhost>
On Fri, Jul 06, 2012 at 11:58:14AM +0000, Marciniszyn, Mike wrote:
> I'm not seeing this on either of my build test systems.
>
> Can you provide your .config file and gcc version?
>
This isn't a GCC warning, it's a sparse warning. It's saying that
your Sparse rcu anotations aren't correct, probably.
I've added Fengguang's other email address in case wfg isn't fixed
yet.
regards,
dan carpenter
next prev parent reply other threads:[~2012-07-06 12:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-06 8:02 [infiniband:for-next 13/14] drivers/infiniband/hw/qib/qib_keys.c:64:23: sparse: incompatible types i wfg
2012-07-06 11:58 ` [infiniband:for-next 13/14] drivers/infiniband/hw/qib/qib_keys.c:64:23: sparse: incompatible typ Marciniszyn, Mike
2012-07-06 12:23 ` Dan Carpenter [this message]
2012-07-06 14:07 ` Fengguang Wu
2012-07-06 20:14 ` Dan Carpenter
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=20120706122354.GB8027@mwanda \
--to=dan.carpenter@oracle.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox