[staging:staging-next] BUILD SUCCESS WITH WARNING 093991aaadf0fbb34184fa37a46e7a157da3f386

2021-08-19 Thread kernel test robot 
-was-for-phy_RFSerialRead()-instead
|   |-- 
drivers-staging-r8188eu-hal-rtl8188e_phycfg.c:warning:expecting-prototype-for-Function().-Prototype-was-for-phy_RFSerialWrite()-instead
|   |-- 
drivers-staging-r8188eu-hal-rtl8188e_phycfg.c:warning:expecting-prototype-for-Function().-Prototype-was-for-rtl8188e_PHY_QueryBBReg()-instead
|   |-- 
drivers-staging-r8188eu-hal-rtl8188e_phycfg.c:warning:expecting-prototype-for-Function().-Prototype-was-for-rtl8188e_PHY_QueryRFReg()-instead
|   |-- 
drivers-staging-r8188eu-hal-rtl8188e_phycfg.c:warning:expecting-prototype-for-Function().-Prototype-was-for-rtl8188e_PHY_SetBBReg()-instead
|   |-- 
drivers-staging-r8188eu-hal-rtl8188e_phycfg.c:warning:expecting-prototype-for-Function().-Prototype-was-for-rtl8188e_PHY_SetRFReg()-instead
|   `-- 
drivers-staging-r8188eu-os_dep-rtw_android.c:warning:This-comment-starts-with-but-isn-t-a-kernel-doc-comment.-Refer-Documentation-doc-guide-kernel-doc.rst
`-- nds32-allyesconfig
|-- 
drivers-staging-r8188eu-core-rtw_ieee80211.c:warning:expecting-prototype-for-ieee802_11_parse_elems().-Prototype-was-for-rtw_ieee802_11_parse_elems()-instead
|-- 
drivers-staging-r8188eu-core-rtw_security.c:warning:This-comment-starts-with-but-isn-t-a-kernel-doc-comment.-Refer-Documentation-doc-guide-kernel-doc.rst
|-- 
drivers-staging-r8188eu-core-rtw_security.c:warning:expecting-prototype-for-omac1_aes_128().-Prototype-was-for-rtw_use_tkipkey_handler()-instead
|-- 
drivers-staging-r8188eu-hal-rtl8188e_phycfg.c:warning:expecting-prototype-for-Function().-Prototype-was-for-phy_CalculateBitShift()-instead
|-- 
drivers-staging-r8188eu-hal-rtl8188e_phycfg.c:warning:expecting-prototype-for-Function().-Prototype-was-for-phy_InitBBRFRegisterDefinition()-instead
|-- 
drivers-staging-r8188eu-hal-rtl8188e_phycfg.c:warning:expecting-prototype-for-Function().-Prototype-was-for-phy_RFSerialRead()-instead
|-- 
drivers-staging-r8188eu-hal-rtl8188e_phycfg.c:warning:expecting-prototype-for-Function().-Prototype-was-for-phy_RFSerialWrite()-instead
|-- 
drivers-staging-r8188eu-hal-rtl8188e_phycfg.c:warning:expecting-prototype-for-Function().-Prototype-was-for-rtl8188e_PHY_QueryBBReg()-instead
|-- 
drivers-staging-r8188eu-hal-rtl8188e_phycfg.c:warning:expecting-prototype-for-Function().-Prototype-was-for-rtl8188e_PHY_QueryRFReg()-instead
|-- 
drivers-staging-r8188eu-hal-rtl8188e_phycfg.c:warning:expecting-prototype-for-Function().-Prototype-was-for-rtl8188e_PHY_SetBBReg()-instead
|-- 
drivers-staging-r8188eu-hal-rtl8188e_phycfg.c:warning:expecting-prototype-for-Function().-Prototype-was-for-rtl8188e_PHY_SetRFReg()-instead
`-- 
drivers-staging-r8188eu-os_dep-rtw_android.c:warning:This-comment-starts-with-but-isn-t-a-kernel-doc-comment.-Refer-Documentation-doc-guide-kernel-doc.rst

elapsed time: 1194m

configs tested: 108
configs skipped: 3

gcc tested configs:
arm defconfig
arm64allyesconfig
arm64   defconfig
arm  allyesconfig
arm  allmodconfig
i386 randconfig-c001-20210819
h8300   h8s-sim_defconfig
powerpc   maple_defconfig
sh   se7751_defconfig
armrealview_defconfig
mips  loongson3_defconfig
s390defconfig
sh  rsk7269_defconfig
arm64alldefconfig
shapsh4ad0a_defconfig
mips   bmips_be_defconfig
m68kdefconfig
powerpc mpc837x_rdb_defconfig
m68kmac_defconfig
powerpc   currituck_defconfig
sh  sh7785lcr_32bit_defconfig
arm  lpd270_defconfig
powerpc mpc8315_rdb_defconfig
powerpc mpc8540_ads_defconfig
powerpc mpc83xx_defconfig
ia64  gensparse_defconfig
x86_64allnoconfig
ia64 allmodconfig
ia64defconfig
ia64 allyesconfig
m68k allmodconfig
m68k allyesconfig
nds32   defconfig
nios2allyesconfig
cskydefconfig
alpha   defconfig
alphaallyesconfig
xtensa   allyesconfig
h8300allyesconfig
arc defconfig
sh   allmodconfig
parisc  defconfig
s390 allyesconfig
s390 allmodconfig
parisc   allyesconfig
i386

[driver-core:driver-core-testing] BUILD SUCCESS bd1e336aa8535a99f339e2d66a611984262221ce

2021-08-19 Thread kernel test robot 
-20210816
x86_64   randconfig-a003-20210816
x86_64   randconfig-a001-20210816
x86_64   randconfig-a005-20210816
x86_64   randconfig-a002-20210816
i386 randconfig-a004-20210818
i386 randconfig-a006-20210818
i386 randconfig-a002-20210818
i386 randconfig-a001-20210818
i386 randconfig-a003-20210818
i386 randconfig-a005-20210818
x86_64   randconfig-a013-20210819
x86_64   randconfig-a011-20210819
x86_64   randconfig-a012-20210819
x86_64   randconfig-a016-20210819
x86_64   randconfig-a014-20210819
x86_64   randconfig-a015-20210819
i386 randconfig-a015-20210819
i386 randconfig-a011-20210819
i386 randconfig-a014-20210819
i386 randconfig-a013-20210819
i386 randconfig-a016-20210819
i386 randconfig-a012-20210819
riscvnommu_k210_defconfig
riscvallyesconfig
riscvnommu_virt_defconfig
riscv allnoconfig
riscv   defconfig
riscv  rv32_defconfig
riscvallmodconfig
x86_64rhel-8.3-kselftests
um   x86_64_defconfig
um i386_defconfig
x86_64  defconfig
x86_64   rhel-8.3
x86_64  kexec

clang tested configs:
i386 randconfig-c001-20210818
i386 randconfig-c001-20210819
x86_64   randconfig-a004-20210819
x86_64   randconfig-a006-20210819
x86_64   randconfig-a003-20210819
x86_64   randconfig-a002-20210819
x86_64   randconfig-a005-20210819
x86_64   randconfig-a001-20210819
i386 randconfig-a004-20210817
i386 randconfig-a003-20210817
i386 randconfig-a001-20210817
i386 randconfig-a002-20210817
i386 randconfig-a006-20210817
i386 randconfig-a005-20210817
i386 randconfig-a004-20210819
i386 randconfig-a006-20210819
i386 randconfig-a001-20210819
i386 randconfig-a002-20210819
i386 randconfig-a003-20210819
i386 randconfig-a005-20210819
x86_64   randconfig-a013-20210818
x86_64   randconfig-a011-20210818
x86_64   randconfig-a012-20210818
x86_64   randconfig-a016-20210818
x86_64   randconfig-a014-20210818
x86_64   randconfig-a015-20210818
i386 randconfig-a015-20210818
i386 randconfig-a011-20210818
i386 randconfig-a013-20210818
i386 randconfig-a014-20210818
i386 randconfig-a016-20210818
i386 randconfig-a012-20210818

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-...@lists.01.org
___
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel

Re: [kbuild-all] Re: [driver-core:driver-core-testing 28/31] WARNING: modpost: vmlinux.o(.text.unlikely+0x156c): Section mismatch in reference from the function bitmap_equal() to the variable .init.da

2021-08-19 Thread Barry Song 
On Thu, Aug 19, 2021 at 6:22 PM Chen, Rong A  wrote:
>
>
>
> On 8/15/2021 8:04 AM, Barry Song wrote:
> > On Sun, Aug 15, 2021 at 5:18 AM Andy Shevchenko
> >  wrote:
> >>
> >> On Sat, Aug 14, 2021 at 4:36 PM Greg Kroah-Hartman
> >>  wrote:
> >>> On Sat, Aug 14, 2021 at 07:03:00PM +0800, kernel test robot wrote:
>  tree:   
>  https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git 
>  driver-core-testing
>  head:   3b35f2a6a625126c57475aa56b5357d8e80b404c
>  commit: 291f93ca339f5b5e6e90ad037bb8271f0f618165 [28/31] lib: 
>  test_bitmap: add bitmap_print_bitmask/list_to_buf test cases
>  config: xtensa-randconfig-r004-20210814 (attached as .config)
>  compiler: xtensa-linux-gcc (GCC) 11.2.0
>  reproduce (this is a W=1 build):
>   wget 
>  https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross 
>  -O ~/bin/make.cross
>   chmod +x ~/bin/make.cross
>   # 
>  https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git/commit/?id=291f93ca339f5b5e6e90ad037bb8271f0f618165
>   git remote add driver-core 
>  https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git
>   git fetch --no-tags driver-core driver-core-testing
>   git checkout 291f93ca339f5b5e6e90ad037bb8271f0f618165
>   # save the attached .config to linux build tree
>   mkdir build_dir
>   COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross 
>  O=build_dir ARCH=xtensa SHELL=/bin/bash
> 
>  If you fix the issue, kindly add following tag as appropriate
>  Reported-by: kernel test robot 
> 
>  All warnings (new ones prefixed by >>, old ones prefixed by <<):
> 
> >> WARNING: modpost: vmlinux.o(.text.unlikely+0x156c): Section mismatch 
> >> in reference from the function bitmap_equal() to the variable 
> >> .init.data:initcall_level_names
>  The function bitmap_equal() references
>  the variable __initdata initcall_level_names.
>  This is often because bitmap_equal lacks a __initdata
>  annotation or the annotation of initcall_level_names is wrong.
> 
>  The below error/warnings are from parent commit:
>  << WARNING: modpost: vmlinux.o(.data+0x1a86d8): Section mismatch in 
>  reference from the variable qed_mfw_legacy_maps to the variable 
>  .init.rodata:__setup_str_initcall_blacklist
>  << WARNING: modpost: vmlinux.o(.data+0x1a87c8): Section mismatch in 
>  reference from the variable qed_mfw_ext_maps to the variable 
>  .init.rodata:__setup_str_initcall_blacklist
>  << WARNING: modpost: vmlinux.o(.data+0x1a8948): Section mismatch in 
>  reference from the variable qede_forced_speed_maps to the variable 
>  .init.rodata:__setup_str_initcall_blacklist
> >>
> >>> Barry, can I get a fix for this?
> >>
> >> Max already pointed out, but I guess you were not in Cc list, that
> >> it's a GCC bug in his opinion, but GCC people don't ack it.
> >> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92938
> >
> > I really don't understand what is going on here. My understanding is
> > this report has nothing to do with the
> > new commit and it doesn't report any valid place where kernel code is wrong.
>
> Hi Barry,
>
> Sorry for the misunderstanding, the warning only changed a little by
> this commit, see:
>
>   The below error/warnings are from parent commit:
>   << WARNING: modpost: vmlinux.o(.data+0x1a86d8): Section mismatch
> in reference from the variable qed_mfw_legacy_maps to the variable
> .init.rodata:__setup_str_initcall_blacklist
>   << WARNING: modpost: vmlinux.o(.data+0x1a87c8): Section mismatch
> in reference from the variable qed_mfw_ext_maps to the variable
> .init.rodata:__setup_str_initcall_blacklist
>   << WARNING: modpost: vmlinux.o(.data+0x1a8948): Section mismatch
> in reference from the variable qede_forced_speed_maps to the variable
> .init.rodata:__setup_str_initcall_blacklist
>
> we'll update the message to give a heavy hint.

Rong, note we have another discussion over here:
https://lore.kernel.org/lkml/20210815032132.14530-1-21cn...@gmail.com/

and a gcc bug was reported one year ago:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92938


>
> Best Regards,
> Rong Chen
>
> >
> > with xtensa gcc 11.1 which is the one i can easily download from here
> > after google:
> > http://kernel.c3sl.ufpr.br/pub/tools/crosstool/
> >
> > i could somehow reproduce this kind of very odd section mismatch
> > report from bitmap:
> > $ ./build-xenta.sh
> >...
> >MODPOST vmlinux.symvers
> > WARNING: modpost: vmlinux.o(.text.unlikely+0x4d64): Section mismatch
> > in reference from the function bitmap_equal() to the variable
> > .init.rodata:__setup_str_initcall_blacklist
> > The function bitmap_equal() references
> > the variable __initconst __setup_str_initcall_blacklist.
> > This is often because bitmap_equal lacks a

Re: [kbuild-all] Re: [driver-core:driver-core-testing 28/31] WARNING: modpost: vmlinux.o(.text.unlikely+0x156c): Section mismatch in reference from the function bitmap_equal() to the variable .init.da

2021-08-19 Thread Chen, Rong A 




On 8/15/2021 8:04 AM, Barry Song wrote:

On Sun, Aug 15, 2021 at 5:18 AM Andy Shevchenko
 wrote:


On Sat, Aug 14, 2021 at 4:36 PM Greg Kroah-Hartman
 wrote:

On Sat, Aug 14, 2021 at 07:03:00PM +0800, kernel test robot wrote:

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git 
driver-core-testing
head:   3b35f2a6a625126c57475aa56b5357d8e80b404c
commit: 291f93ca339f5b5e6e90ad037bb8271f0f618165 [28/31] lib: test_bitmap: add 
bitmap_print_bitmask/list_to_buf test cases
config: xtensa-randconfig-r004-20210814 (attached as .config)
compiler: xtensa-linux-gcc (GCC) 11.2.0
reproduce (this is a W=1 build):
 wget 
https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O 
~/bin/make.cross
 chmod +x ~/bin/make.cross
 # 
https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git/commit/?id=291f93ca339f5b5e6e90ad037bb8271f0f618165
 git remote add driver-core 
https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git
 git fetch --no-tags driver-core driver-core-testing
 git checkout 291f93ca339f5b5e6e90ad037bb8271f0f618165
 # save the attached .config to linux build tree
 mkdir build_dir
 COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross 
O=build_dir ARCH=xtensa SHELL=/bin/bash

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot 

All warnings (new ones prefixed by >>, old ones prefixed by <<):


WARNING: modpost: vmlinux.o(.text.unlikely+0x156c): Section mismatch in 
reference from the function bitmap_equal() to the variable 
.init.data:initcall_level_names

The function bitmap_equal() references
the variable __initdata initcall_level_names.
This is often because bitmap_equal lacks a __initdata
annotation or the annotation of initcall_level_names is wrong.

The below error/warnings are from parent commit:
<< WARNING: modpost: vmlinux.o(.data+0x1a86d8): Section mismatch in reference 
from the variable qed_mfw_legacy_maps to the variable 
.init.rodata:__setup_str_initcall_blacklist
<< WARNING: modpost: vmlinux.o(.data+0x1a87c8): Section mismatch in reference 
from the variable qed_mfw_ext_maps to the variable 
.init.rodata:__setup_str_initcall_blacklist
<< WARNING: modpost: vmlinux.o(.data+0x1a8948): Section mismatch in reference 
from the variable qede_forced_speed_maps to the variable 
.init.rodata:__setup_str_initcall_blacklist



Barry, can I get a fix for this?


Max already pointed out, but I guess you were not in Cc list, that
it's a GCC bug in his opinion, but GCC people don't ack it.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92938


I really don't understand what is going on here. My understanding is
this report has nothing to do with the
new commit and it doesn't report any valid place where kernel code is wrong.


Hi Barry,

Sorry for the misunderstanding, the warning only changed a little by 
this commit, see:


 The below error/warnings are from parent commit:
 << WARNING: modpost: vmlinux.o(.data+0x1a86d8): Section mismatch 
in reference from the variable qed_mfw_legacy_maps to the variable 
.init.rodata:__setup_str_initcall_blacklist
 << WARNING: modpost: vmlinux.o(.data+0x1a87c8): Section mismatch 
in reference from the variable qed_mfw_ext_maps to the variable 
.init.rodata:__setup_str_initcall_blacklist
 << WARNING: modpost: vmlinux.o(.data+0x1a8948): Section mismatch 
in reference from the variable qede_forced_speed_maps to the variable 
.init.rodata:__setup_str_initcall_blacklist


we'll update the message to give a heavy hint.

Best Regards,
Rong Chen



with xtensa gcc 11.1 which is the one i can easily download from here
after google:
http://kernel.c3sl.ufpr.br/pub/tools/crosstool/

i could somehow reproduce this kind of very odd section mismatch
report from bitmap:
$ ./build-xenta.sh
   ...
   MODPOST vmlinux.symvers
WARNING: modpost: vmlinux.o(.text.unlikely+0x4d64): Section mismatch
in reference from the function bitmap_equal() to the variable
.init.rodata:__setup_str_initcall_blacklist
The function bitmap_equal() references
the variable __initconst __setup_str_initcall_blacklist.
This is often because bitmap_equal lacks a __initconst
annotation or the annotation of __setup_str_initcall_blacklist is wrong.

...
WARNING: modpost: lib/find_bit_benchmark.o(.text.unlikely+0x0):
Section mismatch in reference from the (unknown reference) (unknown)
to the variable .init.data:bitmap2
The function (unknown)() references
the variable __initdata bitmap2.
This is often because (unknown) lacks a __initdata
annotation or the annotation of bitmap2 is wrong.
...

But after reverting my commit, it is *still* there:

$ git revert 2069b8b9ce8b758e015ce49225b1fedac4accd9c
[scheduler e158c85c6ccc] Revert "lib: test_bitmap: add
bitmap_print_bitmask/list_to_buf test cases"
  1 file changed, 150 deletions(-)

$ ./build-xenta.sh
...
   MODPOST vmlinux.symvers
WARNING: modpost:

[PATCH v2] drm/bridge: anx7625: enable DSI EOTP

2021-08-19 Thread Xin Ji 
Enable DSI EOTP feature for fixing some panel screen constant shift issue.
Removing MIPI flag MIPI_DSI_MODE_NO_EOT_PACKET to enable DSI EOTP.

Reviewed-by: Robert Foss 
Signed-off-by: Xin Ji 
---
 drivers/gpu/drm/bridge/analogix/anx7625.c | 1 -
 1 file changed, 1 deletion(-)

diff --git a/drivers/gpu/drm/bridge/analogix/anx7625.c 
b/drivers/gpu/drm/bridge/analogix/anx7625.c
index abc8db77bfd3..1a871f6b6822 100644
--- a/drivers/gpu/drm/bridge/analogix/anx7625.c
+++ b/drivers/gpu/drm/bridge/analogix/anx7625.c
@@ -1335,7 +1335,6 @@ static int anx7625_attach_dsi(struct anx7625_data *ctx)
dsi->format = MIPI_DSI_FMT_RGB888;
dsi->mode_flags = MIPI_DSI_MODE_VIDEO   |
MIPI_DSI_MODE_VIDEO_SYNC_PULSE  |
-   MIPI_DSI_MODE_NO_EOT_PACKET |
MIPI_DSI_MODE_VIDEO_HSE;
 
if (mipi_dsi_attach(dsi) < 0) {
-- 
2.25.1

___
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel