[zen-kernel-zen-kernel:5.6/exfat 12/15] fs/exfat/super.c:669:17: error: initialization from incompatible pointer type
by kbuild test robot
Hi Namjae,
First bad commit (maybe != root cause):
tree: https://github.com/zen-kernel/zen-kernel 5.6/exfat
head: 669f683801d1ef2a6716baa6363ef33379be6da5
commit: 42256ca2e038dc7fd23e4c19898877392bd3d512 [12/15] exfat: add exfat in fs/Kconfig and fs/Makefile
config: i386-allyesconfig (attached as .config)
compiler: gcc-7 (Debian 7.4.0-6) 7.4.0
reproduce:
git checkout 42256ca2e038dc7fd23e4c19898877392bd3d512
# 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(a)intel.com>
Note: the zen-kernel-zen-kernel/5.6/exfat HEAD 669f683801d1ef2a6716baa6363ef33379be6da5 builds fine.
It only hurts bisectibility.
All errors (new ones prefixed by >>):
fs/exfat/super.c:222:37: error: macro "fsparam_enum" requires 3 arguments, but only 2 given
fsparam_enum("errors", Opt_errors),
^
fs/exfat/super.c:222:2: error: 'fsparam_enum' undeclared here (not in a function); did you mean 'fs_param_is_enum'?
fsparam_enum("errors", Opt_errors),
^~~~~~~~~~~~
fs_param_is_enum
fs/exfat/super.c:228:39: error: array type has incomplete element type 'struct fs_parameter_enum'
static const struct fs_parameter_enum exfat_param_enums[] = {
^~~~~~~~~~~~~~~~~
fs/exfat/super.c:235:21: error: variable 'exfat_parameters' has initializer but incomplete type
static const struct fs_parameter_description exfat_parameters = {
^~~~~~~~~~~~~~~~~~~~~~~~
fs/exfat/super.c:236:3: error: 'const struct fs_parameter_description' has no member named 'name'
.name = "exfat",
^~~~
fs/exfat/super.c:236:11: warning: excess elements in struct initializer
.name = "exfat",
^~~~~~~
fs/exfat/super.c:236:11: note: (near initialization for 'exfat_parameters')
fs/exfat/super.c:237:3: error: 'const struct fs_parameter_description' has no member named 'specs'
.specs = exfat_param_specs,
^~~~~
fs/exfat/super.c:237:12: warning: excess elements in struct initializer
.specs = exfat_param_specs,
^~~~~~~~~~~~~~~~~
fs/exfat/super.c:237:12: note: (near initialization for 'exfat_parameters')
fs/exfat/super.c:238:3: error: 'const struct fs_parameter_description' has no member named 'enums'
.enums = exfat_param_enums,
^~~~~
fs/exfat/super.c:238:12: warning: excess elements in struct initializer
.enums = exfat_param_enums,
^~~~~~~~~~~~~~~~~
fs/exfat/super.c:238:12: note: (near initialization for 'exfat_parameters')
fs/exfat/super.c: In function 'exfat_parse_param':
fs/exfat/super.c:248:21: error: passing argument 2 of 'fs_parse' from incompatible pointer type [-Werror=incompatible-pointer-types]
opt = fs_parse(fc, &exfat_parameters, param, &result);
^
In file included from fs/exfat/super.c:7:0:
include/linux/fs_parser.h:68:19: note: expected 'const struct fs_parameter_spec *' but argument is of type 'const struct fs_parameter_description *'
static inline int fs_parse(struct fs_context *fc,
^~~~~~~~
fs/exfat/super.c: At top level:
>> fs/exfat/super.c:669:17: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
.parameters = &exfat_parameters,
^
fs/exfat/super.c:669:17: note: (near initialization for 'exfat_fs_type.parameters')
fs/exfat/super.c:235:46: error: storage size of 'exfat_parameters' isn't known
static const struct fs_parameter_description exfat_parameters = {
^~~~~~~~~~~~~~~~
fs/exfat/super.c:228:39: warning: 'exfat_param_enums' defined but not used [-Wunused-variable]
static const struct fs_parameter_enum exfat_param_enums[] = {
^~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +669 fs/exfat/super.c
03e85038b1b69b Namjae Jeon 2020-01-15 664
03e85038b1b69b Namjae Jeon 2020-01-15 665 static struct file_system_type exfat_fs_type = {
03e85038b1b69b Namjae Jeon 2020-01-15 666 .owner = THIS_MODULE,
03e85038b1b69b Namjae Jeon 2020-01-15 667 .name = "exfat",
03e85038b1b69b Namjae Jeon 2020-01-15 668 .init_fs_context = exfat_init_fs_context,
03e85038b1b69b Namjae Jeon 2020-01-15 @669 .parameters = &exfat_parameters,
03e85038b1b69b Namjae Jeon 2020-01-15 670 .kill_sb = kill_block_super,
03e85038b1b69b Namjae Jeon 2020-01-15 671 .fs_flags = FS_REQUIRES_DEV,
03e85038b1b69b Namjae Jeon 2020-01-15 672 };
03e85038b1b69b Namjae Jeon 2020-01-15 673
:::::: The code at line 669 was first introduced by commit
:::::: 03e85038b1b69bde7977190d95e967723b1ba39f exfat: add super block operations
:::::: TO: Namjae Jeon <namjae.jeon(a)samsung.com>
:::::: CC: Jan Alexander Steffens (heftig) <jan.steffens(a)gmail.com>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
1 year, 8 months
Re: [Intel-gfx] [PATCH 1/6] drm/i915/display: Move out code to return the digital_port of the aux ch
by kbuild test robot
Hi "José,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on drm-intel/for-linux-next]
[also build test ERROR on drm-tip/drm-tip next-20200331]
[cannot apply to v5.6]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Jos-Roberto-de-Souza/drm-i915-di...
base: git://anongit.freedesktop.org/drm-intel for-linux-next
config: x86_64-defconfig (attached as .config)
compiler: gcc-7 (Debian 7.4.0-6) 7.4.0
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp(a)intel.com>
All error/warnings (new ones prefixed by >>):
drivers/gpu/drm/i915/display/intel_display_power.c: In function 'icl_tc_phy_aux_power_well_enable':
>> drivers/gpu/drm/i915/display/intel_display_power.c:561:40: error: implicit declaration of function 'aux_ch_to_digital_port'; did you mean 'enc_to_dig_port'? [-Werror=implicit-function-declaration]
struct intel_digital_port *dig_port = aux_ch_to_digital_port(dev_priv, aux_ch);
^~~~~~~~~~~~~~~~~~~~~~
enc_to_dig_port
>> drivers/gpu/drm/i915/display/intel_display_power.c:561:40: warning: initialization makes pointer from integer without a cast [-Wint-conversion]
>> drivers/gpu/drm/i915/display/intel_display_power.c:564:2: error: too many arguments to function 'icl_tc_port_assert_ref_held'
icl_tc_port_assert_ref_held(dev_priv, power_well, dig_port);
^~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/gpu/drm/i915/display/intel_display_power.c:547:13: note: declared here
static void icl_tc_port_assert_ref_held(struct drm_i915_private *dev_priv,
^~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/gpu/drm/i915/display/intel_display_power.c: In function 'icl_tc_phy_aux_power_well_disable':
drivers/gpu/drm/i915/display/intel_display_power.c:593:40: warning: initialization makes pointer from integer without a cast [-Wint-conversion]
struct intel_digital_port *dig_port = aux_ch_to_digital_port(dev_priv, aux_ch);
^~~~~~~~~~~~~~~~~~~~~~
drivers/gpu/drm/i915/display/intel_display_power.c:595:2: error: too many arguments to function 'icl_tc_port_assert_ref_held'
icl_tc_port_assert_ref_held(dev_priv, power_well, dig_port);
^~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/gpu/drm/i915/display/intel_display_power.c:547:13: note: declared here
static void icl_tc_port_assert_ref_held(struct drm_i915_private *dev_priv,
^~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +561 drivers/gpu/drm/i915/display/intel_display_power.c
555
556 static void
557 icl_tc_phy_aux_power_well_enable(struct drm_i915_private *dev_priv,
558 struct i915_power_well *power_well)
559 {
560 enum aux_ch aux_ch = icl_tc_phy_aux_ch(dev_priv, power_well);
> 561 struct intel_digital_port *dig_port = aux_ch_to_digital_port(dev_priv, aux_ch);
562 u32 val;
563
> 564 icl_tc_port_assert_ref_held(dev_priv, power_well, dig_port);
565
566 val = intel_de_read(dev_priv, DP_AUX_CH_CTL(aux_ch));
567 val &= ~DP_AUX_CH_CTL_TBT_IO;
568 if (power_well->desc->hsw.is_tc_tbt)
569 val |= DP_AUX_CH_CTL_TBT_IO;
570 intel_de_write(dev_priv, DP_AUX_CH_CTL(aux_ch), val);
571
572 hsw_power_well_enable(dev_priv, power_well);
573
574 if (INTEL_GEN(dev_priv) >= 12 && !power_well->desc->hsw.is_tc_tbt) {
575 enum tc_port tc_port;
576
577 tc_port = TGL_AUX_PW_TO_TC_PORT(power_well->desc->hsw.idx);
578 intel_de_write(dev_priv, HIP_INDEX_REG(tc_port),
579 HIP_INDEX_VAL(tc_port, 0x2));
580
581 if (intel_de_wait_for_set(dev_priv, DKL_CMN_UC_DW_27(tc_port),
582 DKL_CMN_UC_DW27_UC_HEALTH, 1))
583 drm_warn(&dev_priv->drm,
584 "Timeout waiting TC uC health\n");
585 }
586 }
587
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
1 year, 8 months
Re: [PATCH v11 3/9] KVM: VMX: Set host/guest CET states for vmexit/vmentry
by kbuild test robot
Hi Yang,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on kvm/linux-next]
[also build test ERROR on next-20200331]
[cannot apply to vhost/linux-next tip/auto-latest linus/master linux/master v5.6]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Yang-Weijiang/Introduce-support-...
base: https://git.kernel.org/pub/scm/virt/kvm/kvm.git linux-next
config: i386-allyesconfig (attached as .config)
compiler: gcc-7 (Debian 7.4.0-6) 7.4.0
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(a)intel.com>
All errors (new ones prefixed by >>):
>> arch/x86/kvm/vmx/vmx.c:47:10: fatal error: asm/cet.h: No such file or directory
#include <asm/cet.h>
^~~~~~~~~~~
compilation terminated.
vim +47 arch/x86/kvm/vmx/vmx.c
30
31 #include <asm/apic.h>
32 #include <asm/asm.h>
33 #include <asm/cpu.h>
34 #include <asm/debugreg.h>
35 #include <asm/desc.h>
36 #include <asm/fpu/internal.h>
37 #include <asm/io.h>
38 #include <asm/irq_remapping.h>
39 #include <asm/kexec.h>
40 #include <asm/perf_event.h>
41 #include <asm/mce.h>
42 #include <asm/mmu_context.h>
43 #include <asm/mshyperv.h>
44 #include <asm/spec-ctrl.h>
45 #include <asm/virtext.h>
46 #include <asm/vmx.h>
> 47 #include <asm/cet.h>
48
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
1 year, 8 months
Re: [PATCH 3/4] clk / soc: mediatek: Bind clock and gpu driver for mt2701
by kbuild test robot
Hi Enric,
I love your patch! Yet something to improve:
[auto build test ERROR on next-20200331]
[cannot apply to clk/clk-next robh/for-next rockchip/for-next keystone/next arm64/for-next/core arm-soc/for-next shawnguo/for-next arm/for-next xlnx/master linus/master v5.6 v5.6-rc7 v5.6-rc6 v5.6]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Enric-Balletbo-i-Serra/soc-media...
base: 3eb7cccdb3ae41ebb6a2f5f1ccd2821550c61fe1
config: i386-allyesconfig (attached as .config)
compiler: gcc-7 (Debian 7.4.0-6) 7.4.0
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(a)intel.com>
All errors (new ones prefixed by >>):
>> drivers/clk/mediatek/clk-mt2701-mm.c:107:21: error: 'of_match_clk_mt2701_mm' undeclared here (not in a function)
.of_match_table = of_match_clk_mt2701_mm,
^~~~~~~~~~~~~~~~~~~~~~
vim +/of_match_clk_mt2701_mm +107 drivers/clk/mediatek/clk-mt2701-mm.c
e9862118272aa5 Shunli Wang 2016-11-04 102
e9862118272aa5 Shunli Wang 2016-11-04 103 static struct platform_driver clk_mt2701_mm_drv = {
e9862118272aa5 Shunli Wang 2016-11-04 104 .probe = clk_mt2701_mm_probe,
e9862118272aa5 Shunli Wang 2016-11-04 105 .driver = {
e9862118272aa5 Shunli Wang 2016-11-04 106 .name = "clk-mt2701-mm",
e9862118272aa5 Shunli Wang 2016-11-04 @107 .of_match_table = of_match_clk_mt2701_mm,
e9862118272aa5 Shunli Wang 2016-11-04 108 },
e9862118272aa5 Shunli Wang 2016-11-04 109 };
e9862118272aa5 Shunli Wang 2016-11-04 110
:::::: The code at line 107 was first introduced by commit
:::::: e9862118272aa528e35e54ef9f1e35c217870fd7 clk: mediatek: Add MT2701 clock support
:::::: TO: Shunli Wang <shunli.wang(a)mediatek.com>
:::::: CC: Stephen Boyd <sboyd(a)codeaurora.org>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
1 year, 8 months
[zen-kernel-zen-kernel:5.6/exfat 12/14] fs/exfat/super.c:222:37: error: macro "fsparam_enum" requires 3 arguments, but only 2 given
by kbuild test robot
Hi Namjae,
First bad commit (maybe != root cause):
tree: https://github.com/zen-kernel/zen-kernel 5.6/exfat
head: 800eabb6d277b1cc412857441bbf532bb76dcf56
commit: 42256ca2e038dc7fd23e4c19898877392bd3d512 [12/14] exfat: add exfat in fs/Kconfig and fs/Makefile
config: sh-allmodconfig (attached as .config)
compiler: sh4-linux-gcc (GCC) 9.3.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 42256ca2e038dc7fd23e4c19898877392bd3d512
# save the attached .config to linux build tree
GCC_VERSION=9.3.0 make.cross ARCH=sh
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp(a)intel.com>
All error/warnings (new ones prefixed by >>):
>> fs/exfat/super.c:222:37: error: macro "fsparam_enum" requires 3 arguments, but only 2 given
222 | fsparam_enum("errors", Opt_errors),
| ^
In file included from fs/exfat/super.c:7:
include/linux/fs_parser.h:126: note: macro "fsparam_enum" defined here
126 | #define fsparam_enum(NAME, OPT, array) __fsparam(fs_param_is_enum, NAME, OPT, 0, array)
|
>> fs/exfat/super.c:222:2: error: 'fsparam_enum' undeclared here (not in a function); did you mean 'fs_param_is_enum'?
222 | fsparam_enum("errors", Opt_errors),
| ^~~~~~~~~~~~
| fs_param_is_enum
>> fs/exfat/super.c:228:39: error: array type has incomplete element type 'struct fs_parameter_enum'
228 | static const struct fs_parameter_enum exfat_param_enums[] = {
| ^~~~~~~~~~~~~~~~~
>> fs/exfat/super.c:235:21: error: variable 'exfat_parameters' has initializer but incomplete type
235 | static const struct fs_parameter_description exfat_parameters = {
| ^~~~~~~~~~~~~~~~~~~~~~~~
>> fs/exfat/super.c:236:3: error: 'const struct fs_parameter_description' has no member named 'name'
236 | .name = "exfat",
| ^~~~
>> fs/exfat/super.c:236:11: warning: excess elements in struct initializer
236 | .name = "exfat",
| ^~~~~~~
fs/exfat/super.c:236:11: note: (near initialization for 'exfat_parameters')
>> fs/exfat/super.c:237:3: error: 'const struct fs_parameter_description' has no member named 'specs'
237 | .specs = exfat_param_specs,
| ^~~~~
fs/exfat/super.c:237:12: warning: excess elements in struct initializer
237 | .specs = exfat_param_specs,
| ^~~~~~~~~~~~~~~~~
fs/exfat/super.c:237:12: note: (near initialization for 'exfat_parameters')
>> fs/exfat/super.c:238:3: error: 'const struct fs_parameter_description' has no member named 'enums'
238 | .enums = exfat_param_enums,
| ^~~~~
fs/exfat/super.c:238:12: warning: excess elements in struct initializer
238 | .enums = exfat_param_enums,
| ^~~~~~~~~~~~~~~~~
fs/exfat/super.c:238:12: note: (near initialization for 'exfat_parameters')
fs/exfat/super.c: In function 'exfat_parse_param':
>> fs/exfat/super.c:248:21: error: passing argument 2 of 'fs_parse' from incompatible pointer type [-Werror=incompatible-pointer-types]
248 | opt = fs_parse(fc, &exfat_parameters, param, &result);
| ^~~~~~~~~~~~~~~~~
| |
| const struct fs_parameter_description *
In file included from fs/exfat/super.c:7:
include/linux/fs_parser.h:69:39: note: expected 'const struct fs_parameter_spec *' but argument is of type 'const struct fs_parameter_description *'
69 | const struct fs_parameter_spec *desc,
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~
fs/exfat/super.c: At top level:
>> fs/exfat/super.c:669:17: error: initialization of 'const struct fs_parameter_spec *' from incompatible pointer type 'const struct fs_parameter_description *' [-Werror=incompatible-pointer-types]
669 | .parameters = &exfat_parameters,
| ^
fs/exfat/super.c:669:17: note: (near initialization for 'exfat_fs_type.parameters')
>> fs/exfat/super.c:235:46: error: storage size of 'exfat_parameters' isn't known
235 | static const struct fs_parameter_description exfat_parameters = {
| ^~~~~~~~~~~~~~~~
fs/exfat/super.c:228:39: warning: 'exfat_param_enums' defined but not used [-Wunused-variable]
228 | static const struct fs_parameter_enum exfat_param_enums[] = {
| ^~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +/fsparam_enum +222 fs/exfat/super.c
03e85038b1b69b Namjae Jeon 2020-01-15 213
03e85038b1b69b Namjae Jeon 2020-01-15 214 static const struct fs_parameter_spec exfat_param_specs[] = {
03e85038b1b69b Namjae Jeon 2020-01-15 215 fsparam_u32("uid", Opt_uid),
03e85038b1b69b Namjae Jeon 2020-01-15 216 fsparam_u32("gid", Opt_gid),
03e85038b1b69b Namjae Jeon 2020-01-15 217 fsparam_u32oct("umask", Opt_umask),
03e85038b1b69b Namjae Jeon 2020-01-15 218 fsparam_u32oct("dmask", Opt_dmask),
03e85038b1b69b Namjae Jeon 2020-01-15 219 fsparam_u32oct("fmask", Opt_fmask),
03e85038b1b69b Namjae Jeon 2020-01-15 220 fsparam_u32oct("allow_utime", Opt_allow_utime),
03e85038b1b69b Namjae Jeon 2020-01-15 221 fsparam_string("iocharset", Opt_charset),
03e85038b1b69b Namjae Jeon 2020-01-15 @222 fsparam_enum("errors", Opt_errors),
03e85038b1b69b Namjae Jeon 2020-01-15 223 fsparam_flag("discard", Opt_discard),
03e85038b1b69b Namjae Jeon 2020-01-15 224 fsparam_s32("time_offset", Opt_time_offset),
03e85038b1b69b Namjae Jeon 2020-01-15 225 {}
03e85038b1b69b Namjae Jeon 2020-01-15 226 };
03e85038b1b69b Namjae Jeon 2020-01-15 227
03e85038b1b69b Namjae Jeon 2020-01-15 @228 static const struct fs_parameter_enum exfat_param_enums[] = {
03e85038b1b69b Namjae Jeon 2020-01-15 229 { Opt_errors, "continue", EXFAT_ERRORS_CONT },
03e85038b1b69b Namjae Jeon 2020-01-15 230 { Opt_errors, "panic", EXFAT_ERRORS_PANIC },
03e85038b1b69b Namjae Jeon 2020-01-15 231 { Opt_errors, "remount-ro", EXFAT_ERRORS_RO },
03e85038b1b69b Namjae Jeon 2020-01-15 232 {}
03e85038b1b69b Namjae Jeon 2020-01-15 233 };
03e85038b1b69b Namjae Jeon 2020-01-15 234
03e85038b1b69b Namjae Jeon 2020-01-15 @235 static const struct fs_parameter_description exfat_parameters = {
03e85038b1b69b Namjae Jeon 2020-01-15 @236 .name = "exfat",
03e85038b1b69b Namjae Jeon 2020-01-15 @237 .specs = exfat_param_specs,
03e85038b1b69b Namjae Jeon 2020-01-15 @238 .enums = exfat_param_enums,
03e85038b1b69b Namjae Jeon 2020-01-15 239 };
03e85038b1b69b Namjae Jeon 2020-01-15 240
03e85038b1b69b Namjae Jeon 2020-01-15 241 static int exfat_parse_param(struct fs_context *fc, struct fs_parameter *param)
03e85038b1b69b Namjae Jeon 2020-01-15 242 {
03e85038b1b69b Namjae Jeon 2020-01-15 243 struct exfat_sb_info *sbi = fc->s_fs_info;
03e85038b1b69b Namjae Jeon 2020-01-15 244 struct exfat_mount_options *opts = &sbi->options;
03e85038b1b69b Namjae Jeon 2020-01-15 245 struct fs_parse_result result;
03e85038b1b69b Namjae Jeon 2020-01-15 246 int opt;
03e85038b1b69b Namjae Jeon 2020-01-15 247
03e85038b1b69b Namjae Jeon 2020-01-15 @248 opt = fs_parse(fc, &exfat_parameters, param, &result);
03e85038b1b69b Namjae Jeon 2020-01-15 249 if (opt < 0)
03e85038b1b69b Namjae Jeon 2020-01-15 250 return opt;
03e85038b1b69b Namjae Jeon 2020-01-15 251
03e85038b1b69b Namjae Jeon 2020-01-15 252 switch (opt) {
03e85038b1b69b Namjae Jeon 2020-01-15 253 case Opt_uid:
03e85038b1b69b Namjae Jeon 2020-01-15 254 opts->fs_uid = make_kuid(current_user_ns(), result.uint_32);
03e85038b1b69b Namjae Jeon 2020-01-15 255 break;
03e85038b1b69b Namjae Jeon 2020-01-15 256 case Opt_gid:
03e85038b1b69b Namjae Jeon 2020-01-15 257 opts->fs_gid = make_kgid(current_user_ns(), result.uint_32);
03e85038b1b69b Namjae Jeon 2020-01-15 258 break;
03e85038b1b69b Namjae Jeon 2020-01-15 259 case Opt_umask:
03e85038b1b69b Namjae Jeon 2020-01-15 260 opts->fs_fmask = result.uint_32;
03e85038b1b69b Namjae Jeon 2020-01-15 261 opts->fs_dmask = result.uint_32;
03e85038b1b69b Namjae Jeon 2020-01-15 262 break;
03e85038b1b69b Namjae Jeon 2020-01-15 263 case Opt_dmask:
03e85038b1b69b Namjae Jeon 2020-01-15 264 opts->fs_dmask = result.uint_32;
03e85038b1b69b Namjae Jeon 2020-01-15 265 break;
03e85038b1b69b Namjae Jeon 2020-01-15 266 case Opt_fmask:
03e85038b1b69b Namjae Jeon 2020-01-15 267 opts->fs_fmask = result.uint_32;
03e85038b1b69b Namjae Jeon 2020-01-15 268 break;
03e85038b1b69b Namjae Jeon 2020-01-15 269 case Opt_allow_utime:
03e85038b1b69b Namjae Jeon 2020-01-15 270 opts->allow_utime = result.uint_32 & 0022;
03e85038b1b69b Namjae Jeon 2020-01-15 271 break;
03e85038b1b69b Namjae Jeon 2020-01-15 272 case Opt_charset:
03e85038b1b69b Namjae Jeon 2020-01-15 273 exfat_free_iocharset(sbi);
03e85038b1b69b Namjae Jeon 2020-01-15 274 opts->iocharset = kstrdup(param->string, GFP_KERNEL);
03e85038b1b69b Namjae Jeon 2020-01-15 275 if (!opts->iocharset)
03e85038b1b69b Namjae Jeon 2020-01-15 276 return -ENOMEM;
03e85038b1b69b Namjae Jeon 2020-01-15 277 break;
03e85038b1b69b Namjae Jeon 2020-01-15 278 case Opt_errors:
03e85038b1b69b Namjae Jeon 2020-01-15 279 opts->errors = result.uint_32;
03e85038b1b69b Namjae Jeon 2020-01-15 280 break;
03e85038b1b69b Namjae Jeon 2020-01-15 281 case Opt_discard:
03e85038b1b69b Namjae Jeon 2020-01-15 282 opts->discard = 1;
03e85038b1b69b Namjae Jeon 2020-01-15 283 break;
03e85038b1b69b Namjae Jeon 2020-01-15 284 case Opt_time_offset:
03e85038b1b69b Namjae Jeon 2020-01-15 285 /*
03e85038b1b69b Namjae Jeon 2020-01-15 286 * GMT+-12 zones may have DST corrections so at least
03e85038b1b69b Namjae Jeon 2020-01-15 287 * 13 hours difference is needed. Make the limit 24
03e85038b1b69b Namjae Jeon 2020-01-15 288 * just in case someone invents something unusual.
03e85038b1b69b Namjae Jeon 2020-01-15 289 */
03e85038b1b69b Namjae Jeon 2020-01-15 290 if (result.int_32 < -24 * 60 || result.int_32 > 24 * 60)
03e85038b1b69b Namjae Jeon 2020-01-15 291 return -EINVAL;
03e85038b1b69b Namjae Jeon 2020-01-15 292 opts->time_offset = result.int_32;
03e85038b1b69b Namjae Jeon 2020-01-15 293 break;
03e85038b1b69b Namjae Jeon 2020-01-15 294 default:
03e85038b1b69b Namjae Jeon 2020-01-15 295 return -EINVAL;
03e85038b1b69b Namjae Jeon 2020-01-15 296 }
03e85038b1b69b Namjae Jeon 2020-01-15 297
03e85038b1b69b Namjae Jeon 2020-01-15 298 return 0;
03e85038b1b69b Namjae Jeon 2020-01-15 299 }
03e85038b1b69b Namjae Jeon 2020-01-15 300
:::::: The code at line 222 was first introduced by commit
:::::: 03e85038b1b69bde7977190d95e967723b1ba39f exfat: add super block operations
:::::: TO: Namjae Jeon <namjae.jeon(a)samsung.com>
:::::: CC: Jan Alexander Steffens (heftig) <jan.steffens(a)gmail.com>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
1 year, 8 months
Re: [PATCH 2/4] clk / soc: mediatek: Bind clock and gpu driver for mt2712
by kbuild test robot
Hi Enric,
I love your patch! Yet something to improve:
[auto build test ERROR on next-20200331]
[cannot apply to clk/clk-next robh/for-next rockchip/for-next keystone/next arm64/for-next/core arm-soc/for-next shawnguo/for-next arm/for-next xlnx/master linus/master v5.6 v5.6-rc7 v5.6-rc6 v5.6]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Enric-Balletbo-i-Serra/soc-media...
base: 3eb7cccdb3ae41ebb6a2f5f1ccd2821550c61fe1
config: i386-allyesconfig (attached as .config)
compiler: gcc-7 (Debian 7.4.0-6) 7.4.0
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(a)intel.com>
All errors (new ones prefixed by >>):
>> drivers/clk/mediatek/clk-mt2712-mm.c:154:21: error: 'of_match_clk_mt2712_mm' undeclared here (not in a function)
.of_match_table = of_match_clk_mt2712_mm,
^~~~~~~~~~~~~~~~~~~~~~
vim +/of_match_clk_mt2712_mm +154 drivers/clk/mediatek/clk-mt2712-mm.c
e2f744a82d725a weiyi.lu(a)mediatek.com 2017-10-23 149
e2f744a82d725a weiyi.lu(a)mediatek.com 2017-10-23 150 static struct platform_driver clk_mt2712_mm_drv = {
e2f744a82d725a weiyi.lu(a)mediatek.com 2017-10-23 151 .probe = clk_mt2712_mm_probe,
e2f744a82d725a weiyi.lu(a)mediatek.com 2017-10-23 152 .driver = {
e2f744a82d725a weiyi.lu(a)mediatek.com 2017-10-23 153 .name = "clk-mt2712-mm",
e2f744a82d725a weiyi.lu(a)mediatek.com 2017-10-23 @154 .of_match_table = of_match_clk_mt2712_mm,
e2f744a82d725a weiyi.lu(a)mediatek.com 2017-10-23 155 },
e2f744a82d725a weiyi.lu(a)mediatek.com 2017-10-23 156 };
e2f744a82d725a weiyi.lu(a)mediatek.com 2017-10-23 157
:::::: The code at line 154 was first introduced by commit
:::::: e2f744a82d725ab55091cccfb8e527b4220471f0 clk: mediatek: Add MT2712 clock support
:::::: TO: weiyi.lu(a)mediatek.com <weiyi.lu(a)mediatek.com>
:::::: CC: Stephen Boyd <sboyd(a)codeaurora.org>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
1 year, 8 months
[frank-w-bpi-r2-4.14:5.6-main 23/32] drivers/misc/mediatek/connectivity/common/common_detect/wmt_gpio.h:24:10: fatal error: osal.h: No such file or directory
by kbuild test robot
tree: https://github.com/frank-w/BPI-R2-4.14 5.6-main
head: 4fae43b208567f97bfb418f89c6934d0d8dc1534
commit: e00e4a70aa3252dd01134f30ce738c17e091da2c [23/32] timekeeping32: reverting changes for wifi-driver
config: arm-allmodconfig (attached as .config)
compiler: arm-linux-gnueabi-gcc (GCC) 9.3.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 e00e4a70aa3252dd01134f30ce738c17e091da2c
# save the attached .config to linux build tree
GCC_VERSION=9.3.0 make.cross ARCH=arm
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp(a)intel.com>
All errors (new ones prefixed by >>):
In file included from drivers/misc/mediatek/connectivity/common/common_detect/wmt_detect.c:24:
>> drivers/misc/mediatek/connectivity/common/common_detect/wmt_gpio.h:24:10: fatal error: osal.h: No such file or directory
24 | #include "osal.h"
| ^~~~~~~~
compilation terminated.
vim +24 drivers/misc/mediatek/connectivity/common/common_detect/wmt_gpio.h
843d8eb0bcd3b5 Frank Wunderlich 2020-02-10 17
843d8eb0bcd3b5 Frank Wunderlich 2020-02-10 18 #include <linux/of.h>
843d8eb0bcd3b5 Frank Wunderlich 2020-02-10 19 #include <linux/of_gpio.h>
843d8eb0bcd3b5 Frank Wunderlich 2020-02-10 20 #include <linux/pinctrl/consumer.h>
843d8eb0bcd3b5 Frank Wunderlich 2020-02-10 21 #include <linux/pinctrl/pinctrl.h>
843d8eb0bcd3b5 Frank Wunderlich 2020-02-10 22 #include <linux/gpio.h>
843d8eb0bcd3b5 Frank Wunderlich 2020-02-10 23 #include <linux/platform_device.h>
843d8eb0bcd3b5 Frank Wunderlich 2020-02-10 @24 #include "osal.h"
843d8eb0bcd3b5 Frank Wunderlich 2020-02-10 25
:::::: The code at line 24 was first introduced by commit
:::::: 843d8eb0bcd3b53370aabe9f1c231c0f5cf8ca7d mt6625l: add driver folder
:::::: TO: Frank Wunderlich <frank-w(a)public-files.de>
:::::: CC: Frank Wunderlich <frank-w(a)public-files.de>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
1 year, 8 months
Re: [PATCH 2/4] kvm: async_pf: Send faulting gva address in case of error
by kbuild test robot
Hi Vivek,
I love your patch! Yet something to improve:
[auto build test ERROR on vhost/linux-next]
[also build test ERROR on linus/master v5.6]
[cannot apply to kvm/linux-next linux/master next-20200331]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url: https://github.com/0day-ci/linux/commits/Vivek-Goyal/kvm-x86-async_pf-Add...
base: https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git linux-next
config: i386-allyesconfig (attached as .config)
compiler: gcc-7 (Debian 7.4.0-6) 7.4.0
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(a)intel.com>
All errors (new ones prefixed by >>):
arch/x86/kvm/svm.c: In function 'nested_svm_exit_special':
>> arch/x86/kvm/svm.c:3237:58: error: invalid operands to binary == (have 'struct kvm_apf_reason' and 'int')
if (!npt_enabled && svm->vcpu.arch.apf.host_apf_reason == 0)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^~
arch/x86/kvm/svm.c: In function 'svm_vcpu_run':
>> arch/x86/kvm/svm.c:5930:40: error: too few arguments to function 'kvm_read_and_reset_pf_reason'
svm->vcpu.arch.apf.host_apf_reason = kvm_read_and_reset_pf_reason();
^~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from include/uapi/linux/kvm_para.h:36:0,
from include/linux/kvm_para.h:5,
from include/linux/kvm_host.h:32,
from arch/x86/kvm/svm.c:17:
arch/x86/include/asm/kvm_para.h:93:6: note: declared here
void kvm_read_and_reset_pf_reason(struct kvm_apf_reason *reason);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~
vim +3237 arch/x86/kvm/svm.c
ab2f4d73ebc334 Ladi Prosek 2017-06-21 3220
410e4d573d9b7f Joerg Roedel 2009-08-07 3221 static int nested_svm_exit_special(struct vcpu_svm *svm)
4c2161aed55c29 Joerg Roedel 2009-08-07 3222 {
cf74a78b229d07 Alexander Graf 2008-11-25 3223 u32 exit_code = svm->vmcb->control.exit_code;
4c2161aed55c29 Joerg Roedel 2009-08-07 3224
cf74a78b229d07 Alexander Graf 2008-11-25 3225 switch (exit_code) {
cf74a78b229d07 Alexander Graf 2008-11-25 3226 case SVM_EXIT_INTR:
cf74a78b229d07 Alexander Graf 2008-11-25 3227 case SVM_EXIT_NMI:
ff47a49b235e59 Joerg Roedel 2010-04-22 3228 case SVM_EXIT_EXCP_BASE + MC_VECTOR:
410e4d573d9b7f Joerg Roedel 2009-08-07 3229 return NESTED_EXIT_HOST;
cf74a78b229d07 Alexander Graf 2008-11-25 3230 case SVM_EXIT_NPF:
e02317153e7715 Joerg Roedel 2010-02-24 3231 /* For now we are always handling NPFs when using them */
cf74a78b229d07 Alexander Graf 2008-11-25 3232 if (npt_enabled)
410e4d573d9b7f Joerg Roedel 2009-08-07 3233 return NESTED_EXIT_HOST;
cf74a78b229d07 Alexander Graf 2008-11-25 3234 break;
cf74a78b229d07 Alexander Graf 2008-11-25 3235 case SVM_EXIT_EXCP_BASE + PF_VECTOR:
631bc487822093 Gleb Natapov 2010-10-14 3236 /* When we're shadowing, trap PFs, but not async PF */
1261bfa326f5e9 Wanpeng Li 2017-07-13 @3237 if (!npt_enabled && svm->vcpu.arch.apf.host_apf_reason == 0)
410e4d573d9b7f Joerg Roedel 2009-08-07 3238 return NESTED_EXIT_HOST;
cf74a78b229d07 Alexander Graf 2008-11-25 3239 break;
cf74a78b229d07 Alexander Graf 2008-11-25 3240 default:
cf74a78b229d07 Alexander Graf 2008-11-25 3241 break;
cf74a78b229d07 Alexander Graf 2008-11-25 3242 }
410e4d573d9b7f Joerg Roedel 2009-08-07 3243
410e4d573d9b7f Joerg Roedel 2009-08-07 3244 return NESTED_EXIT_CONTINUE;
cf74a78b229d07 Alexander Graf 2008-11-25 3245 }
cf74a78b229d07 Alexander Graf 2008-11-25 3246
:::::: The code at line 3237 was first introduced by commit
:::::: 1261bfa326f5e903166498628a1894edce0caabc KVM: async_pf: Add L1 guest async_pf #PF vmexit handler
:::::: TO: Wanpeng Li <wanpeng.li(a)hotmail.com>
:::::: CC: Radim Krčmář <rkrcmar(a)redhat.com>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
1 year, 8 months