[linux-next:master 6182/6533] net/rds/message.c:70:27: sparse: symbol 'rds_info_from_znotifier' was not declared. Should it be static?

mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed

From: kbuild test robot <fengguang.wu@intel.com>
To: Sowmini Varadhan <sowmini.varadhan@oracle.com>
Cc: kbuild-all@01.org,
	Santosh Shilimkar <santosh.shilimkar@oracle.com>,
	netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
	rds-devel@oss.oracle.com, linux-kernel@vger.kernel.org
Subject: [linux-next:master 6182/6533] net/rds/message.c:70:27: sparse: symbol 'rds_info_from_znotifier' was not declared. Should it be static?
Date: Thu, 8 Mar 2018 19:37:29 +0800	[thread overview]
Message-ID: <201803081946.adQaZcK5%fengguang.wu@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   c6f1a8c953479b390458e36fb838d96199a5f466
commit: 9426bbc6de99b8649d897b94e8f5916b58195643 [6182/6533] rds: use list structure to track information for zerocopy completion notification
reproduce:
        # apt-get install sparse
        git checkout 9426bbc6de99b8649d897b94e8f5916b58195643
        make ARCH=x86_64 allmodconfig
        make C=1 CF=-D__CHECK_ENDIAN__


sparse warnings: (new ones prefixed by >>)

>> net/rds/message.c:70:27: sparse: symbol 'rds_info_from_znotifier' was not declared. Should it be static?
   net/rds/message.c:358:5: sparse: symbol 'rds_message_zcopy_from_user' was not declared. Should it be static?

Please review and possibly fold the followup patch.

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

next             reply	other threads:[~2018-03-08 11:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-08 11:37 kbuild test robot [this message]
2018-03-08 11:37 ` [RFC PATCH linux-next] rds: rds_info_from_znotifier() can be static kbuild test robot
2018-03-09  2:54   ` David Miller

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=201803081946.adQaZcK5%fengguang.wu@intel.com \
    --to=fengguang.wu@intel.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rds-devel@oss.oracle.com \
    --cc=santosh.shilimkar@oracle.com \
    --cc=sowmini.varadhan@oracle.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®