Re: [PATCH v3 1/1] drm/bridge: ps8640: Rework power state handling

[Enric Balletbo i Serra <enric.balletbo@collabora.com>]

Hi,

On 27/8/20 21:34, kernel test robot wrote:
> Hi Enric,
> 
> I love your patch! Perhaps something to improve:
> 
> [auto build test WARNING on drm-tip/drm-tip]
> [cannot apply to linux/master drm-intel/for-linux-next linus/master v5.9-rc2]
> [If your patch is applied to the wrong git tree, kindly drop us a note.
> And when submitting patch, we suggest to use '--base' as documented in
> https://git-scm.com/docs/git-format-patch]
> 
> url:    https://github.com/0day-ci/linux/commits/Enric-Balletbo-i-Serra/drm-bridge-ps8640-Make-sure-all-needed-is-powered-to-get-the-EDID/20200827-170009
> base:   git://anongit.freedesktop.org/drm/drm-tip drm-tip
> config: riscv-randconfig-r001-20200827 (attached as .config)
> compiler: riscv32-linux-gcc (GCC) 9.3.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
>         # save the attached .config to linux build tree
>         COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=riscv 
> 
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
> 
> All warnings (new ones prefixed by >>, old ones prefixed by <<):
> 
> << WARNING: modpost: vmlinux.o(__ex_table+0xed0): Section mismatch in reference from the (unknown reference) (unknown) to the variable .debug_str:.LASF1611
>>> WARNING: modpost: vmlinux.o(__ex_table+0xf40): Section mismatch in reference from the (unknown reference) (unknown) to the variable .debug_str:.LASF1482
> FATAL: modpost: The relocation at __ex_table+0xf40 references
> section ".debug_str" which is not executable, IOW
> it is not possible for the kernel to fault
> at that address.  Something is seriously wrong
> and should be fixed.
> 

Hmm, is this really a build problem introduce by the patch ? I'll try to
investigate a bit more but looks to me that there is another problem and a false
positive.

Thanks,
  Enric


> ---
> 0-DAY CI Kernel Test Service, Intel Corporation
> https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
>