From: kbuild test robot <lkp@intel.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: kbuild-all@lists.01.org, linux-fsdevel@vger.kernel.org,
Al Viro <viro@zeniv.linux.org.uk>
Subject: [vfs:merge.nfs-fs_parse.1 13/26] fs/nfs/fs_context.c:177:11: error: initialization from incompatible pointer type
Date: Thu, 6 Feb 2020 18:56:40 +0800 [thread overview]
Message-ID: <202002061836.K7TCFpOy%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2217 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git merge.nfs-fs_parse.1
head: 7a53c2012d523b81902e4c7dbd5bc171f91ee125
commit: 7984d6fd4bd61472532addd4fa247775b353fcc5 [13/26] fs_parser: remove fs_parameter_description name field
config: alpha-defconfig (attached as .config)
compiler: alpha-linux-gcc (GCC) 7.5.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 7984d6fd4bd61472532addd4fa247775b353fcc5
# save the attached .config to linux build tree
GCC_VERSION=7.5.0 make.cross ARCH=alpha
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
Note: the vfs/merge.nfs-fs_parse.1 HEAD 7a53c2012d523b81902e4c7dbd5bc171f91ee125 builds fine.
It only hurts bisectibility.
All errors (new ones prefixed by >>):
fs/nfs/fs_context.c:177:3: error: 'const struct fs_parameter_description' has no member named 'name'
.name = "nfs",
^~~~
>> fs/nfs/fs_context.c:177:11: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
.name = "nfs",
^~~~~
fs/nfs/fs_context.c:177:11: note: (near initialization for 'nfs_fs_parameters.specs')
cc1: some warnings being treated as errors
vim +177 fs/nfs/fs_context.c
9954bf92c0cddd David Howells 2019-12-10 175
e38bb238ed8ce2 Scott Mayhew 2019-12-10 176 static const struct fs_parameter_description nfs_fs_parameters = {
e38bb238ed8ce2 Scott Mayhew 2019-12-10 @177 .name = "nfs",
e38bb238ed8ce2 Scott Mayhew 2019-12-10 178 .specs = nfs_param_specs,
9954bf92c0cddd David Howells 2019-12-10 179 };
9954bf92c0cddd David Howells 2019-12-10 180
:::::: The code at line 177 was first introduced by commit
:::::: e38bb238ed8ce280a217629294ba51dc217c5a2c NFS: Convert mount option parsing to use functionality from fs_parser.h
:::::: TO: Scott Mayhew <smayhew@redhat.com>
:::::: CC: Anna Schumaker <Anna.Schumaker@Netapp.com>
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 13337 bytes --]
reply other threads:[~2020-02-06 10:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202002061836.K7TCFpOy%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sandeen@sandeen.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;
as well as URLs for NNTP newsgroup(s).