From: kernel test robot <lkp@intel.com>
To: Chuck Lever <cel@kernel.org>, NeilBrown <neilb@ownmail.net>,
Jeff Layton <jlayton@kernel.org>,
Olga Kornievskaia <okorniev@redhat.com>,
Dai Ngo <dai.ngo@oracle.com>, Tom Talpey <tom@talpey.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-nfs@vger.kernel.org, Chuck Lever <chuck.lever@oracle.com>
Subject: Re: [PATCH v3 11/14] lockd: Move xdr.h from include/linux/lockd/ to fs/lockd/
Date: Tue, 27 Jan 2026 12:56:47 +0800 [thread overview]
Message-ID: <202601271247.TFeb5MO5-lkp@intel.com> (raw)
In-Reply-To: <20260126195535.154697-12-cel@kernel.org>
Hi Chuck,
kernel test robot noticed the following build warnings:
[auto build test WARNING on trondmy-nfs/linux-next]
[also build test WARNING on brauner-vfs/vfs.all linus/master v6.19-rc7 next-20260126]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Chuck-Lever/lockd-Simplify-cast_status-in-svcproc-c/20260127-035838
base: git://git.linux-nfs.org/projects/trondmy/linux-nfs.git linux-next
patch link: https://lore.kernel.org/r/20260126195535.154697-12-cel%40kernel.org
patch subject: [PATCH v3 11/14] lockd: Move xdr.h from include/linux/lockd/ to fs/lockd/
config: s390-defconfig (https://download.01.org/0day-ci/archive/20260127/202601271247.TFeb5MO5-lkp@intel.com/config)
compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project 9b8addffa70cee5b2acc5454712d9cf78ce45710)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260127/202601271247.TFeb5MO5-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202601271247.TFeb5MO5-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from fs/nfsd/lockd.c:11:
>> include/linux/lockd/bind.h:76:64: warning: declaration of 'struct file_lock' will not be visible outside of this function [-Wvisibility]
76 | extern int nlmclnt_proc(struct nlm_host *host, int cmd, struct file_lock *fl, void *data);
| ^
1 warning generated.
vim +76 include/linux/lockd/bind.h
b1ece737f44f91d Benjamin Coddington 2017-04-11 75
b1ece737f44f91d Benjamin Coddington 2017-04-11 @76 extern int nlmclnt_proc(struct nlm_host *host, int cmd, struct file_lock *fl, void *data);
40373b125de6bab Trond Myklebust 2019-04-09 77 extern int lockd_up(struct net *net, const struct cred *cred);
e3f70eadb7dddfb Stanislav Kinsbursky 2012-03-29 78 extern void lockd_down(struct net *net);
^1da177e4c3f415 Linus Torvalds 2005-04-16 79
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
parent reply other threads:[~2026-01-27 4:57 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20260126195535.154697-12-cel@kernel.org>]
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=202601271247.TFeb5MO5-lkp@intel.com \
--to=lkp@intel.com \
--cc=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=dai.ngo@oracle.com \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=neilb@ownmail.net \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=okorniev@redhat.com \
--cc=tom@talpey.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