Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Benjamin Coddington <bcodding@redhat.com>
Cc: Latchesar Ionkov <lucho@ionkov.net>,
	Christoph Hellwig <hch@infradead.org>,
	Trond Myklebust <trond.myklebust@primarydata.com>,
	"J. Bruce Fields" <bfields@fieldses.org>,
	Bob Peterson <rpeterso@redhat.com>,
	Jeff Layton <jlayton@poochiereds.net>,
	devel@driverdev.osuosl.org, linux-cifs@vger.kernel.org,
	Sage Weil <sage@redhat.com>, Miklos Szeredi <miklos@szeredi.hu>,
	Steve French <sfrench@samba.org>,
	cluster-devel@redhat.com, Eric Van Hensbergen <ericvh@gmail.com>,
	Christine Caulfield <ccaulfie@redhat.com>,
	v9fs-developer@lists.sourceforge.net,
	Ilya Dryomov <idryomov@gmail.com>,
	fuse-devel@lists.sourceforge.net, Mark Fasheh <mfasheh@suse.com>,
	Oleg Drokin <oleg.drokin@intel.com>,
	Julia Lawall <Julia.Lawall@lip6.fr>,
	David Teigland <teigland@redhat.com>,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	ceph-devel@vger.kernel.org, Abdul Hussain <habdul@visteon.com>,
	Steven Whitehouse
Subject: Re: [PATCH 3/3] locks: cleanup posix_lock_inode_wait and flock_lock_inode_wait
Date: Fri, 23 Oct 2015 00:36:55 +0800	[thread overview]
Message-ID: <201510230020.vZvDxsE7%fengguang.wu@intel.com> (raw)
In-Reply-To: <ded792d8fdcba562a1c74fd14fefcb387debc4b1.1445524157.git.bcodding@redhat.com>

Hi Benjamin,

[auto build test WARNING on jlayton/linux-next -- if it's inappropriate base, please suggest rules for selecting the more suitable base]

url:    https://github.com/0day-ci/linux/commits/Benjamin-Coddington/locks-introduce-locks_lock_inode_wait/20151022-233848
reproduce:
        # apt-get install sparse
        make ARCH=x86_64 allmodconfig
        make C=1 CF=-D__CHECK_ENDIAN__


sparse warnings: (new ones prefixed by >>)

>> fs/locks.c:1176:5: sparse: symbol 'posix_lock_inode_wait' was not declared. Should it be static?
>> fs/locks.c:1863:5: sparse: symbol 'flock_lock_inode_wait' 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

      parent reply	other threads:[~2015-10-22 16:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-22 15:35 [PATCH 0/3] Minor cleanup for locks API Benjamin Coddington
2015-10-22 15:35 ` [PATCH 1/3] locks: introduce locks_lock_inode_wait() Benjamin Coddington
     [not found]   ` <daf0d3941f34438c1fbdc94a5f3a47c2b22f3ee8.1445524157.git.bcodding-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-10-22 15:59     ` kbuild test robot
2015-10-22 16:21   ` Benjamin Coddington
2015-10-22 15:35 ` [PATCH 2/3] Move locks API users to locks_lock_inode_wait() Benjamin Coddington
2015-10-22 15:35 ` [PATCH 3/3] locks: cleanup posix_lock_inode_wait and flock_lock_inode_wait Benjamin Coddington
2015-10-22 16:36   ` [RFC PATCH] locks: posix_lock_inode_wait() can be static kbuild test robot
2015-10-22 16:36   ` kbuild test robot [this message]

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=201510230020.vZvDxsE7%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=Julia.Lawall@lip6.fr \
    --cc=bcodding@redhat.com \
    --cc=bfields@fieldses.org \
    --cc=ccaulfie@redhat.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=cluster-devel@redhat.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=ericvh@gmail.com \
    --cc=fuse-devel@lists.sourceforge.net \
    --cc=habdul@visteon.com \
    --cc=hch@infradead.org \
    --cc=idryomov@gmail.com \
    --cc=jlayton@poochiereds.net \
    --cc=linux-cifs@vger.kernel.org \
    --cc=lucho@ionkov.net \
    --cc=mfasheh@suse.com \
    --cc=miklos@szeredi.hu \
    --cc=oleg.drokin@intel.com \
    --cc=rpeterso@redhat.com \
    --cc=sage@redhat.com \
    --cc=sfrench@samba.org \
    --cc=teigland@redhat.com \
    --cc=trond.myklebust@primarydata.com \
    --cc=v9fs-developer@lists.sourceforge.net \
    --cc=viro@zeniv.linux.org.uk \
    /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