mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <fengguang.wu@intel.com>
To: Praveen Madhavan <praveenm@chelsio.com>
Cc: kbuild-all@01.org,
	"James E.J. Bottomley" <JBottomley@parallels.com>,
	Hariprasad Shenai <hariprasad@chelsio.com>,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [net-next:master 62/63] drivers/scsi/csiostor/csio_hw.c:2012:5: sparse: symbol 'csio_hw_prep_fw' was not declared. Should it be static?
Date: Fri, 9 Jan 2015 12:52:13 +0800	[thread overview]
Message-ID: <201501091252.dqPVA7db%fengguang.wu@intel.com> (raw)

tree:   git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git master
head:   fb57720daf6e56ba453414b5e8dd9cb3c0c80257
commit: f40e74ffa3de44f7ef4c09653b070dd115ab7fbe [62/63] csiostor:firmware upgrade fix
reproduce:
  # apt-get install sparse
  git checkout f40e74ffa3de44f7ef4c09653b070dd115ab7fbe
  make ARCH=x86_64 allmodconfig
  make C=1 CF=-D__CHECK_ENDIAN__


sparse warnings: (new ones prefixed by >>)

   drivers/scsi/csiostor/csio_hw.c:259:17: sparse: cast to restricted __le32
   drivers/scsi/csiostor/csio_hw.c:536:31: sparse: incorrect type in assignment (different base types)
   drivers/scsi/csiostor/csio_hw.c:536:31:    expected unsigned int [unsigned] [usertype] <noident>
   drivers/scsi/csiostor/csio_hw.c:536:31:    got restricted __be32 [usertype] <noident>
>> drivers/scsi/csiostor/csio_hw.c:2012:5: sparse: symbol 'csio_hw_prep_fw' was not declared. Should it be static?

Please review and possibly fold the followup patch.

---
0-DAY kernel test infrastructure                Open Source Technology Center
http://lists.01.org/mailman/listinfo/kbuild                 Intel Corporation

                 reply	other threads:[~2015-01-09  4:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=201501091252.dqPVA7db%fengguang.wu@intel.com \
    --to=fengguang.wu@intel.com \
    --cc=JBottomley@parallels.com \
    --cc=hariprasad@chelsio.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=praveenm@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
all inboxes | Powered by JetHome®