From: kbuild test robot <lkp@intel.com>
To: Carmeli Tamir <carmeli.tamir@gmail.com>
Cc: kbuild-all@01.org, carmeli.tamir@gmail.com,
viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] Use list.h instead of file_system_type next
Date: Tue, 7 May 2019 01:33:31 +0800 [thread overview]
Message-ID: <201905070115.iyrJR1im%lkp@intel.com> (raw)
In-Reply-To: <20190504094549.10021-2-carmeli.tamir@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2072 bytes --]
Hi Carmeli,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v5.1 next-20190506]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Carmeli-Tamir/Use-list-h-instead-of-file_system_type-next/20190506-214032
config: i386-randconfig-i2-201918 (attached as .config)
compiler: gcc-5 (Debian 5.5.0-3) 5.4.1 20171010
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> fs/ocfs2/super.c:1250:2: error: unknown field 'next' specified in initializer
.next = NULL
^
vim +/next +1250 fs/ocfs2/super.c
ccd979bdb Mark Fasheh 2005-12-15 1243
ccd979bdb Mark Fasheh 2005-12-15 1244 static struct file_system_type ocfs2_fs_type = {
ccd979bdb Mark Fasheh 2005-12-15 1245 .owner = THIS_MODULE,
ccd979bdb Mark Fasheh 2005-12-15 1246 .name = "ocfs2",
152a08366 Al Viro 2010-07-25 1247 .mount = ocfs2_mount,
8ed6b2370 Goldwyn Rodrigues 2014-04-03 1248 .kill_sb = kill_block_super,
1ba9da2ff Mark Fasheh 2006-09-08 1249 .fs_flags = FS_REQUIRES_DEV|FS_RENAME_DOES_D_MOVE,
ccd979bdb Mark Fasheh 2005-12-15 @1250 .next = NULL
ccd979bdb Mark Fasheh 2005-12-15 1251 };
914177054 Eric W. Biederman 2013-03-07 1252 MODULE_ALIAS_FS("ocfs2");
ccd979bdb Mark Fasheh 2005-12-15 1253
:::::: The code at line 1250 was first introduced by commit
:::::: ccd979bdbce9fba8412beb3f1de68a9d0171b12c [PATCH] OCFS2: The Second Oracle Cluster Filesystem
:::::: TO: Mark Fasheh <mark.fasheh@oracle.com>
:::::: CC: Joel Becker <joel.becker@oracle.com>
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 31111 bytes --]
next prev parent reply other threads:[~2019-05-06 17:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-04 9:45 [PATCH 0/2] Refactor file_systems to use the kernel's list Carmeli Tamir
2019-05-04 9:45 ` [PATCH 1/2] Use list.h instead of file_system_type next Carmeli Tamir
2019-05-04 13:20 ` Al Viro
2019-05-04 13:45 ` Matthew Wilcox
2019-05-05 18:25 ` Tamir Carmeli
2019-05-06 2:49 ` Matthew Wilcox
2019-05-06 15:16 ` kbuild test robot
2019-05-06 17:33 ` kbuild test robot [this message]
2019-05-04 9:45 ` [PATCH 2/2] Changed unsigned param type to unsigned int Carmeli Tamir
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=201905070115.iyrJR1im%lkp@intel.com \
--to=lkp@intel.com \
--cc=carmeli.tamir@gmail.com \
--cc=kbuild-all@01.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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.