From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: Hiral Patel <hiralpat@cisco.com>,
linux-scsi@vger.kernel.org, Narsimhulu Musini <nmusini@cisco.com>
Subject: Re: [scsi:for-next 23/27] drivers/scsi/fnic/fnic_scsi.c:183:35: sparse: invalid assignment: &=
Date: Tue, 29 Jan 2013 14:16:54 +1100 [thread overview]
Message-ID: <1359429414.2408.22.camel@dabdike> (raw)
In-Reply-To: <50cf2343.OFwbZqu4+cv8MZmU%fengguang.wu@intel.com>
On Mon, 2012-12-17 at 21:50 +0800, kbuild test robot wrote:
> tree: git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git for-next
> head: e3ff197a750d2912d0bb2a0161c23c18bad250ad
> commit: 188061001ac78b40780af042dd2156e2213e29ed [23/27] [SCSI] fnic:fixing issues in device and firmware reset code
>
>
> sparse warnings:
>
> + drivers/scsi/fnic/fnic_scsi.c:183:35: sparse: invalid assignment: &=
> drivers/scsi/fnic/fnic_scsi.c:183:35: left side has type restricted unsigned long long
> drivers/scsi/fnic/fnic_scsi.c:183:35: right side has type unsigned long long
> drivers/scsi/fnic/fnic_scsi.c:185:35: sparse: invalid assignment: |=
> drivers/scsi/fnic/fnic_scsi.c:185:35: left side has type restricted unsigned long long
> drivers/scsi/fnic/fnic_scsi.c:185:35: right side has type unsigned long long
I still haven't seen fixes for these patches. I've flushed the fnic
patches from the tree pending resolution. That means the only remaining
fnic patches I have are
1/10 fnic: updated MAINTAINERS list
2/10 fnic: fix for trusted cos
Please fix this and the smatch issues and resubmit the other eight.
Thanks,
James
next prev parent reply other threads:[~2013-01-29 3:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-17 13:50 [scsi:for-next 23/27] drivers/scsi/fnic/fnic_scsi.c:183:35: sparse: invalid assignment: &= kbuild test robot
2013-01-29 3:16 ` James Bottomley [this message]
2013-01-30 0:17 ` Hiral Patel (hiralpat)
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=1359429414.2408.22.camel@dabdike \
--to=james.bottomley@hansenpartnership.com \
--cc=fengguang.wu@intel.com \
--cc=hiralpat@cisco.com \
--cc=linux-scsi@vger.kernel.org \
--cc=nmusini@cisco.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