mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <fengguang.wu@intel.com>
To: Erez Shitrit <erezsh@mellanox.com>
Cc: kbuild-all@01.org, Roland Dreier <roland@kernel.org>,
	Sean Hefty <sean.hefty@intel.com>,
	Hal Rosenstock <hal.rosenstock@gmail.com>,
	Doug Ledford <dledford@redhat.com>,
	linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [amirv:for-upstream 52/62] drivers/infiniband/ulp/ipoib/ipoib_multicast.c:735:5: sparse: symbol 'handle_neigh_state_change' was not declared. Should it be static?
Date: Tue, 14 Apr 2015 19:52:53 +0800	[thread overview]
Message-ID: <201504141939.n2Kcfmrx%fengguang.wu@intel.com> (raw)

tree:   git://flatbed.openfabrics.org/~amirv/linux.git for-upstream
head:   66a75344a2e5a8e8483cfd6ab1db1c0fbcb56fda
commit: cbaa5ae8702fea9670d77daf95f35b4d38822ad0 [52/62] IB/ipoib: Add cleanup to sendonly multicast objects [ib-next:ipoib-s1]
reproduce:
  # apt-get install sparse
  git checkout cbaa5ae8702fea9670d77daf95f35b4d38822ad0
  make ARCH=x86_64 allmodconfig
  make C=1 CF=-D__CHECK_ENDIAN__


sparse warnings: (new ones prefixed by >>)

>> drivers/infiniband/ulp/ipoib/ipoib_multicast.c:735:5: sparse: symbol 'handle_neigh_state_change' 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-04-14 11:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-14 11:52 kbuild test robot [this message]
2015-04-14 11:52 ` [PATCH amirv] IB/ipoib: Add cleanup to sendonly multicast objects [ib-next: handle_neigh_state_change() can be static kbuild test robot

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=201504141939.n2Kcfmrx%fengguang.wu@intel.com \
    --to=fengguang.wu@intel.com \
    --cc=dledford@redhat.com \
    --cc=erezsh@mellanox.com \
    --cc=hal.rosenstock@gmail.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=roland@kernel.org \
    --cc=sean.hefty@intel.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®