The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: kbuild test robot <fengguang.wu@intel.com>
To: Alan Tull <atull@opensource.altera.com>
Cc: kbuild-all@01.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: [socfpga-nex:for_next-fpgamgr-without-overlays-v4.3 8/9] drivers/staging/fpga/socfpga.c:655:25: sparse: symbol 'socfpga_fpga_ops' was not declared. Should it be static?
Date: Thu, 11 Dec 2014 09:43:24 +0800	[thread overview]
Message-ID: <201412110903.GCuPHwdi%fengguang.wu@intel.com> (raw)

tree:   git://git.rocketboards.org/linux-socfpga-next for_next-fpgamgr-without-overlays-v4.3
head:   7920447fc75922e9a72db640cddf890d75a30e0d
commit: 99aa2d008ce7a2a925368bfddd53ae83d307fb38 [8/9] staging: fpga manager: add driver for socfpga fpga manager
reproduce:
  # apt-get install sparse
  git checkout 99aa2d008ce7a2a925368bfddd53ae83d307fb38
  make ARCH=x86_64 allmodconfig
  make C=1 CF=-D__CHECK_ENDIAN__


sparse warnings: (new ones prefixed by >>)

>> drivers/staging/fpga/socfpga.c:655:25: sparse: symbol 'socfpga_fpga_ops' 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:[~2014-12-11  1:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-11  1:43 kbuild test robot [this message]
2014-12-11  1:43 ` [PATCH socfpga-nex] staging: fpga manager: socfpga_fpga_ops can be static kbuild test robot
2014-12-11 20:40   ` One Thousand Gnomes
2014-12-12 15:31     ` atull

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=201412110903.GCuPHwdi%fengguang.wu@intel.com \
    --to=fengguang.wu@intel.com \
    --cc=atull@opensource.altera.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@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