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
WARNING: multiple messages have this Message-ID (diff)
From: kbuild test robot <lkp@intel.com>
To: Benjamin Coddington <bcodding@redhat.com>
Cc: kbuild-all@01.org, Jeff Layton <jlayton@poochiereds.net>,
"J. Bruce Fields" <bfields@fieldses.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Latchesar Ionkov <lucho@ionkov.net>,
linux-fsdevel@vger.kernel.org,
Trond Myklebust <trond.myklebust@primarydata.com>,
devel@driverdev.osuosl.org, Yan Zheng <zyan@redhat.com>,
cluster-devel@redhat.com, Sage Weil <sage@redhat.com>,
Miklos Szeredi <miklos@szeredi.hu>,
Christoph Hellwig <hch@infradead.org>,
fuse-devel@lists.sourceforge.net,
Christine Caulfield <ccaulfie@redhat.com>,
v9fs-developer@lists.sourceforge.net,
Ilya Dryomov <idryomov@gmail.com>,
linux-cifs@vger.kernel.org,
Eric Van Hensbergen <ericvh@gmail.com>,
Mark Fasheh <mfasheh@suse.com>,
Oleg Drokin <oleg.drokin@intel.com>,
Julia Lawall <Julia.Lawall@lip6.fr>,
David Teigland <teigland@redhat.com>,
Joel Becker <jlbec@evilplan.org>,
ceph-devel@vger.kernel.org, Abdul Hussain <habdul@visteon.com>,
Steven Whitehouse <swhiteho@redhat.com>,
linux-nfs@vger.kernel.org,
Andreas Dilger <andreas.dilger@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
samba-technical@lists.samba.org, linux-kernel@vger.kernel.org,
Steve French <sfrench@samba.org>,
Bob Peterson <rpeterso@redhat.com>,
Ron Minnich <rminnich@sandia.gov>,
Anna Schumaker <anna.schumaker@netapp.com>,
ocfs2-devel@oss.oracle.com, lustre-devel@lists.lustre.org
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
WARNING: multiple messages have this Message-ID (diff)
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
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
WARNING: multiple messages have this Message-ID (diff)
From: kbuild test robot <lkp@intel.com>
To: lustre-devel@lists.lustre.org
Subject: [lustre-devel] [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
WARNING: multiple messages have this Message-ID (diff)
From: kbuild test robot <lkp@intel.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [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
next prev parent reply other threads:[~2015-10-22 16:36 UTC|newest]
Thread overview: 38+ 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 ` [Cluster-devel] " Benjamin Coddington
2015-10-22 15:35 ` [lustre-devel] " Benjamin Coddington
2015-10-22 15:35 ` Benjamin Coddington
2015-10-22 15:35 ` Benjamin Coddington
2015-10-22 15:35 ` [PATCH 1/3] locks: introduce locks_lock_inode_wait() Benjamin Coddington
2015-10-22 15:35 ` [Cluster-devel] " Benjamin Coddington
2015-10-22 15:35 ` [lustre-devel] " Benjamin Coddington
2015-10-22 15:35 ` Benjamin Coddington
2015-10-22 15:35 ` 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 15:59 ` [Cluster-devel] " kbuild test robot
2015-10-22 15:59 ` [lustre-devel] " kbuild test robot
2015-10-22 15:59 ` kbuild test robot
2015-10-22 16:21 ` Benjamin Coddington
2015-10-22 16:21 ` [Cluster-devel] " Benjamin Coddington
2015-10-22 16:21 ` [lustre-devel] " Benjamin Coddington
2015-10-22 16:21 ` Benjamin Coddington
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 ` [Cluster-devel] " Benjamin Coddington
2015-10-22 15:35 ` [lustre-devel] " Benjamin Coddington
2015-10-22 15:35 ` Benjamin Coddington
2015-10-22 15:35 ` 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 15:35 ` [Cluster-devel] " Benjamin Coddington
2015-10-22 15:35 ` [lustre-devel] " Benjamin Coddington
2015-10-22 15:35 ` Benjamin Coddington
2015-10-22 15:35 ` 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 ` [Cluster-devel] " kbuild test robot
2015-10-22 16:36 ` [lustre-devel] " kbuild test robot
2015-10-22 16:36 ` kbuild test robot
2015-10-22 16:36 ` kbuild test robot [this message]
2015-10-22 16:36 ` [Cluster-devel] [PATCH 3/3] locks: cleanup posix_lock_inode_wait and flock_lock_inode_wait kbuild test robot
2015-10-22 16:36 ` [lustre-devel] " kbuild test robot
2015-10-22 16:36 ` kbuild test robot
2015-10-22 16:36 ` 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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.