From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [android-common:android-4.14-stable 2/5] fs/incfs/main.c:40:22: error: initializer element is not constant
Date: Fri, 11 Dec 2020 21:46:05 +0800 [thread overview]
Message-ID: <202012112102.oyVgzmoq-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 5972 bytes --]
tree: https://android.googlesource.com/kernel/common android-4.14-stable
head: 8278cda5d9767db20d87f2d97e135534c43b07ae
commit: b38636bf5933cdfc7490ed5bb0cec3893a646bab [2/5] ANDROID: Incremental fs: Add v2 feature flag
config: i386-randconfig-c001-20201209 (attached as .config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce (this is a W=1 build):
git remote add android-common https://android.googlesource.com/kernel/common
git fetch --no-tags android-common android-4.14-stable
git checkout b38636bf5933cdfc7490ed5bb0cec3893a646bab
# save the attached .config to linux build tree
make W=1 ARCH=i386
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
In file included from include/linux/kobject.h:21:0,
from include/linux/module.h:17,
from fs/incfs/main.c:7:
>> fs/incfs/main.c:40:22: error: initializer element is not constant
DECLARE_FEATURE_FLAG(corefs);
^
include/linux/sysfs.h:117:10: note: in definition of macro '__ATTR_RO'
.show = _name##_show, \
^~~~~
fs/incfs/main.c:38:36: note: in expansion of macro '_DECLARE_FEATURE_FLAG'
#define DECLARE_FEATURE_FLAG(name) _DECLARE_FEATURE_FLAG(name)
^~~~~~~~~~~~~~~~~~~~~
fs/incfs/main.c:40:1: note: in expansion of macro 'DECLARE_FEATURE_FLAG'
DECLARE_FEATURE_FLAG(corefs);
^~~~~~~~~~~~~~~~~~~~
fs/incfs/main.c:40:22: note: (near initialization for 'corefs_attr.show')
DECLARE_FEATURE_FLAG(corefs);
^
include/linux/sysfs.h:117:10: note: in definition of macro '__ATTR_RO'
.show = _name##_show, \
^~~~~
fs/incfs/main.c:38:36: note: in expansion of macro '_DECLARE_FEATURE_FLAG'
#define DECLARE_FEATURE_FLAG(name) _DECLARE_FEATURE_FLAG(name)
^~~~~~~~~~~~~~~~~~~~~
fs/incfs/main.c:40:1: note: in expansion of macro 'DECLARE_FEATURE_FLAG'
DECLARE_FEATURE_FLAG(corefs);
^~~~~~~~~~~~~~~~~~~~
fs/incfs/main.c:41:22: error: initializer element is not constant
DECLARE_FEATURE_FLAG(zstd);
^
include/linux/sysfs.h:117:10: note: in definition of macro '__ATTR_RO'
.show = _name##_show, \
^~~~~
fs/incfs/main.c:38:36: note: in expansion of macro '_DECLARE_FEATURE_FLAG'
#define DECLARE_FEATURE_FLAG(name) _DECLARE_FEATURE_FLAG(name)
^~~~~~~~~~~~~~~~~~~~~
fs/incfs/main.c:41:1: note: in expansion of macro 'DECLARE_FEATURE_FLAG'
DECLARE_FEATURE_FLAG(zstd);
^~~~~~~~~~~~~~~~~~~~
fs/incfs/main.c:41:22: note: (near initialization for 'zstd_attr.show')
DECLARE_FEATURE_FLAG(zstd);
^
include/linux/sysfs.h:117:10: note: in definition of macro '__ATTR_RO'
.show = _name##_show, \
^~~~~
fs/incfs/main.c:38:36: note: in expansion of macro '_DECLARE_FEATURE_FLAG'
#define DECLARE_FEATURE_FLAG(name) _DECLARE_FEATURE_FLAG(name)
^~~~~~~~~~~~~~~~~~~~~
fs/incfs/main.c:41:1: note: in expansion of macro 'DECLARE_FEATURE_FLAG'
DECLARE_FEATURE_FLAG(zstd);
^~~~~~~~~~~~~~~~~~~~
fs/incfs/main.c:42:22: error: initializer element is not constant
DECLARE_FEATURE_FLAG(v2);
^
include/linux/sysfs.h:117:10: note: in definition of macro '__ATTR_RO'
.show = _name##_show, \
^~~~~
fs/incfs/main.c:38:36: note: in expansion of macro '_DECLARE_FEATURE_FLAG'
#define DECLARE_FEATURE_FLAG(name) _DECLARE_FEATURE_FLAG(name)
^~~~~~~~~~~~~~~~~~~~~
fs/incfs/main.c:42:1: note: in expansion of macro 'DECLARE_FEATURE_FLAG'
DECLARE_FEATURE_FLAG(v2);
^~~~~~~~~~~~~~~~~~~~
fs/incfs/main.c:42:22: note: (near initialization for 'v2_attr.show')
DECLARE_FEATURE_FLAG(v2);
^
include/linux/sysfs.h:117:10: note: in definition of macro '__ATTR_RO'
.show = _name##_show, \
^~~~~
fs/incfs/main.c:38:36: note: in expansion of macro '_DECLARE_FEATURE_FLAG'
#define DECLARE_FEATURE_FLAG(name) _DECLARE_FEATURE_FLAG(name)
^~~~~~~~~~~~~~~~~~~~~
fs/incfs/main.c:42:1: note: in expansion of macro 'DECLARE_FEATURE_FLAG'
DECLARE_FEATURE_FLAG(v2);
^~~~~~~~~~~~~~~~~~~~
vim +40 fs/incfs/main.c
> 7 #include <linux/module.h>
8
9 #include <uapi/linux/incrementalfs.h>
10
11 #include "vfs.h"
12
13 #define INCFS_NODE_FEATURES "features"
14
15 static struct file_system_type incfs_fs_type = {
16 .owner = THIS_MODULE,
17 .name = INCFS_NAME,
18 .mount = incfs_mount_fs,
19 .kill_sb = incfs_kill_sb,
20 .fs_flags = 0
21 };
22
23 static struct kobject *sysfs_root, *featurefs_root;
24
25 static ssize_t supported(struct kobject *kobj,
26 struct kobj_attribute *attr, char *buff)
27 {
28 return snprintf(buff, PAGE_SIZE, "supported\n");
29 }
30
31 typedef ssize_t (*const attr_show)(struct kobject *kobj,
32 struct kobj_attribute *attr, char *buff);
33
34 #define _DECLARE_FEATURE_FLAG(name) \
35 static attr_show name##_show = supported; \
36 static struct kobj_attribute name##_attr = __ATTR_RO(name)
37
38 #define DECLARE_FEATURE_FLAG(name) _DECLARE_FEATURE_FLAG(name)
39
> 40 DECLARE_FEATURE_FLAG(corefs);
41 DECLARE_FEATURE_FLAG(zstd);
42 DECLARE_FEATURE_FLAG(v2);
43
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 33393 bytes --]
reply other threads:[~2020-12-11 13:46 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=202012112102.oyVgzmoq-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
/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.