From: Bart Van Assche <bart.vanassche@sandisk.com>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: "kbuild-all@01.org" <kbuild-all@01.org>,
James Bottomley <JBottomley@Odin.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [scsi:misc 35/39] drivers/scsi/qla2xxx/qla_iocb.c:1972:18: sparse: incorrect type in assignment (different base types)
Date: Wed, 26 Aug 2015 14:52:41 -0700 [thread overview]
Message-ID: <55DE3529.2020703@sandisk.com> (raw)
In-Reply-To: <201508270507.SZtS5QlR%fengguang.wu@intel.com>
On 08/26/2015 02:04 PM, kbuild test robot wrote:
> tree: git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git misc
> head: 8d16366b5f23e928e5fd22eaeaceeb0356921fc0
> commit: 118e2ef9df2297147706d21d2a1dfeefea878c5a [35/39] qla2xxx: Avoid that sparse complains about duplicate [noderef] attributes
> reproduce:
> # apt-get install sparse
> git checkout 118e2ef9df2297147706d21d2a1dfeefea878c5a
> make ARCH=x86_64 allmodconfig
> make C=1 CF=-D__CHECK_ENDIAN__
>
>
> sparse warnings: (new ones prefixed by >>)
>
>>> drivers/scsi/qla2xxx/qla_iocb.c:1972:18: sparse: incorrect type in assignment (different base types)
Hello,
The scope of the patches that just have been queued in James' scsi-misc
branch is to address the sparse warnings reported without
CF=-D__CHECK_ENDIAN__. Addressing the endianness warnings in the qla2xxx
driver is a separate (large) effort. If anyone is volunteering, please
let me know.
Bart.
prev parent reply other threads:[~2015-08-26 21:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-26 21:01 [scsi:misc 35/39] drivers/scsi/qla2xxx/qla_iocb.c:1972:18: sparse: incorrect type in assignment (different base types) kbuild test robot
2015-08-26 21:52 ` Bart Van Assche [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=55DE3529.2020703@sandisk.com \
--to=bart.vanassche@sandisk.com \
--cc=JBottomley@Odin.com \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-scsi@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.