From: Fengguang Wu <fengguang.wu@intel.com>
To: Naresh Kumar Inna <naresh@chelsio.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
James Bottomley <JBottomley@Parallels.com>
Subject: Re: [scsi:misc 36/36] drivers/scsi/csiostor/csio_attr.c:92:41: sparse: incorrect type in assignment (different base types)
Date: Fri, 16 Nov 2012 22:58:19 +0800 [thread overview]
Message-ID: <20121116145819.GC5726@localhost> (raw)
In-Reply-To: <50A61169.3010709@chelsio.com>
Hi Naresh,
On Fri, Nov 16, 2012 at 03:41:53PM +0530, Naresh Kumar Inna wrote:
> On 11/15/2012 11:59 PM, kbuild test robot wrote:
> > tree: git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git misc
> > head: 0779fa137a73170b6c796fdb476f1455ba67b9aa
> > commit: 0779fa137a73170b6c796fdb476f1455ba67b9aa [36/36] [SCSI] csiostor: Chelsio FCoE offload driver
> >
> >
> > sparse warnings:
> >
>
> Thanks for your report.
My pleasure!
> My run of 'make C=2' to run sparse never reported these. Is there
> someway I can run your tool locally so I can clean up my next set of
> patches before sending them?
This will enable more sparse type checks:
make C=1 CF=-D__CHECK_ENDIAN__
> With respect to the warnings, will correct type-casting help me get rid
> of most of them?
As long as the type-casting is *correct* ;-)
Thanks,
Fengguang
prev parent reply other threads:[~2012-11-16 14:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-15 18:29 [scsi:misc 36/36] drivers/scsi/csiostor/csio_attr.c:92:41: sparse: incorrect type in assignment (different base types) kbuild test robot
2012-11-16 10:11 ` Naresh Kumar Inna
2012-11-16 14:58 ` Fengguang Wu [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=20121116145819.GC5726@localhost \
--to=fengguang.wu@intel.com \
--cc=JBottomley@Parallels.com \
--cc=linux-scsi@vger.kernel.org \
--cc=naresh@chelsio.com \
/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).