Re: [PATCH v3] drm/panel-edp: Add BOE NV153WUM-N42, CMN N153JCA-ELK, CSW MNF307QS3-2

[Doug Anderson]

Hi,

On Sat, Mar 21, 2026 at 7:03 AM kernel test robot <lkp@xxxxxxxxx> wrote:
>
> Hi Alvin1,
>
> kernel test robot noticed the following build warnings:
>
> [auto build test WARNING on drm-misc/drm-misc-next]
> [also build test WARNING on linus/master v7.0-rc4]
> [cannot apply to next-20260320]
> [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#_base_tree_information]
>
> url:    https://github.com/intel-lab-lkp/linux/commits/Alvin1-Chen/drm-panel-edp-Add-BOE-NV153WUM-N42-CMN-N153JCA-ELK-CSW-MNF307QS3-2/20260320-084718
> base:   https://gitlab.freedesktop.org/drm/misc/kernel.git drm-misc-next
> patch link:    https://lore.kernel.org/r/20260319050938.556235-1-alvin1.chen%40lcfc.corp-partner.google.com
> patch subject: [PATCH v3] drm/panel-edp: Add BOE NV153WUM-N42, CMN N153JCA-ELK, CSW  MNF307QS3-2
> config: i386-randconfig-2006-20250825 (https://download.01.org/0day-ci/archive/20260321/202603211444.JZ4VbAPo-lkp@xxxxxxxxx/config)
> compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260321/202603211444.JZ4VbAPo-lkp@xxxxxxxxx/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@xxxxxxxxx>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202603211444.JZ4VbAPo-lkp@xxxxxxxxx/
>
> All warnings (new ones prefixed by >>):
>
>    drivers/gpu/drm/panel/panel-edp.c:1893:1: error: expected expression before '{' token
>     1893 | { \
>          | ^
>    drivers/gpu/drm/panel/panel-edp.c:2028:9: note: in expansion of macro 'EDP_PANEL_ENTRY'
>     2028 | +       EDP_PANEL_ENTRY('B', 'O', 'E', 0x0db3, &delay_200_500_e80, "NV153WUM-N42"),
>          |         ^~~~~~~~~~~~~~~

I think this is the issue I already reported where your patch had an
extra "+" in it. I fixed it when applying the patch. I think the
kernel robot here was just testing the patch itself, not what landed.

So nothing needs to be done here.

-Doug