mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Markus Probst <markus.probst@posteo.de>
To: kernel test robot <lkp@intel.com>,
	ChunAn Wu <an.wu@canonical.com>,
	 linux-serial@vger.kernel.org,
	platform-driver-x86@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
	 gregkh@linuxfoundation.org, jirislaby@kernel.org,
	hansg@kernel.org,  ilpo.jarvinen@linux.intel.com,
	mpearson-lenovo@squebb.ca,  derekjohn.clark@gmail.com
Subject: Re: [PATCH v4] platform/x86: dell-uart-backlight: Bind through normal serdev matching
Date: Sat, 24 Oct 2026 12:03:41 +0000	[thread overview]
Message-ID: <0197324d19f5c68e46dab41e22dbfc4c1bc34813.camel@posteo.de> (raw)
In-Reply-To: <202610241920.GJiRENj2-lkp@intel.com>

[-- Attachment #1: Type: text/plain, Size: 5336 bytes --]

On Sat, 2026-10-24 at 19:59 +0800, kernel test robot wrote:
> Hi ChunAn,
> 
> kernel test robot noticed the following build errors:
> 
> [auto build test ERROR on driver-core/driver-core-testing]
> [also build test ERROR on driver-core/driver-core-next driver-core/driver-core-linus linus/master v7.3 next-20261022]
> [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/ChunAn-Wu/platform-x86-dell-uart-backlight-Bind-through-normal-serdev-matching/20261024-102929
> base:   driver-core/driver-core-testing
> patch link:    https://lore.kernel.org/r/20261024022930.2704030-3-an.wu%40canonical.com
> patch subject: [PATCH v4] platform/x86: dell-uart-backlight: Bind through normal serdev matching
> config: i386-randconfig-1007-20261024 (https://download.01.org/0day-ci/archive/20261024/202610241920.GJiRENj2-lkp@intel.com/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/20261024/202610241920.GJiRENj2-lkp@intel.com/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@intel.com>
> > Closes: https://lore.kernel.org/oe-kbuild-all/202610241920.GJiRENj2-lkp@intel.com/
> 
> All error/warnings (new ones prefixed by >>):
> 
> > > drivers/platform/x86/dell/dell-uart-backlight.c:328:38: error: array type has incomplete element type 'struct serdev_device_id'
>      328 | static const struct serdev_device_id dell_uart_bl_serdev_id[] = {
>          |                                      ^~~~~~~~~~~~~~~~~~~~~~
> > > drivers/platform/x86/dell/dell-uart-backlight.c:338:10: error: 'struct serdev_device_driver' has no member named 'id_table'
>      338 |         .id_table = dell_uart_bl_serdev_id,
>          |          ^~~~~~~~
>    drivers/platform/x86/dell/dell-uart-backlight.c: In function 'dell_uart_bl_pdev_probe':
> > > drivers/platform/x86/dell/dell-uart-backlight.c:363:15: error: too many arguments to function 'serdev_device_add'
>      363 |         ret = serdev_device_add(serdev, KBUILD_MODNAME);
>          |               ^~~~~~~~~~~~~~~~~
>    In file included from drivers/platform/x86/dell/dell-uart-backlight.c:19:
>    include/linux/serdev.h:161:5: note: declared here
>      161 | int serdev_device_add(struct serdev_device *);
>          |     ^~~~~~~~~~~~~~~~~
>    drivers/platform/x86/dell/dell-uart-backlight.c: At top level:
> > > drivers/platform/x86/dell/dell-uart-backlight.c:328:38: warning: 'dell_uart_bl_serdev_id' defined but not used [-Wunused-variable]
>      328 | static const struct serdev_device_id dell_uart_bl_serdev_id[] = {
>          |                                      ^~~~~~~~~~~~~~~~~~~~~~
> 
> 
> vim +328 drivers/platform/x86/dell/dell-uart-backlight.c
> 
>    327	
>  > 328	static const struct serdev_device_id dell_uart_bl_serdev_id[] = {
>    329		{ KBUILD_MODNAME },
>    330		{ }
>    331	};
>    332	
>    333	static struct serdev_device_driver dell_uart_bl_serdev_driver = {
>    334		.probe = dell_uart_bl_serdev_probe,
>    335		.driver = {
>    336			.name = KBUILD_MODNAME,
>    337		},
>  > 338		.id_table = dell_uart_bl_serdev_id,
>    339	};
>    340	
>    341	static int dell_uart_bl_pdev_probe(struct platform_device *pdev)
>    342	{
>    343		enum acpi_backlight_type bl_type;
>    344		struct serdev_device *serdev;
>    345		struct device *ctrl_dev;
>    346		int ret;
>    347	
>    348		bl_type = acpi_video_get_backlight_type();
>    349		if (bl_type != acpi_backlight_dell_uart) {
>    350			dev_dbg(&pdev->dev, "Not loading (ACPI backlight type = %d)\n", bl_type);
>    351			return -ENODEV;
>    352		}
>    353	
>    354		ctrl_dev = get_serdev_controller("DELL0501", NULL, 0, "serial0");
>    355		if (IS_ERR(ctrl_dev))
>    356			return PTR_ERR(ctrl_dev);
>    357	
>    358		serdev = serdev_device_alloc(to_serdev_controller(ctrl_dev));
>    359		put_device(ctrl_dev);
>    360		if (!serdev)
>    361			return -ENOMEM;
>    362	
>  > 363		ret = serdev_device_add(serdev, KBUILD_MODNAME);
>    364		if (ret) {
>    365			dev_err(&pdev->dev, "error %d adding serdev\n", ret);
>    366			serdev_device_put(serdev);
>    367			return ret;
>    368		}
>    369	
>    370		ret = serdev_device_driver_register(&dell_uart_bl_serdev_driver);
>    371		if (ret)
>    372			goto err_remove_serdev;
>    373	
>    374		/* So that dell_uart_bl_pdev_remove() can remove the serdev */
>    375		platform_set_drvdata(pdev, serdev);
>    376		return 0;
>    377	
>    378	err_remove_serdev:
>    379		serdev_device_remove(serdev);
>    380		return ret;
>    381	}
>    382	
> 
> --
> 0-DAY CI Kernel Test Service
> https://github.com/intel/lkp-tests/wiki

Because of the missing "2/3" in the subject line it likely has applied
it as first patch. I assume that was by mistake, given you also resent
the same patch again with the correct subject line.

Anyway, this report should be meaningless.

Thanks
- Markus Probst


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 870 bytes --]

  reply	other threads:[~2026-10-24 12:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-24  2:29 [PATCH v4 0/3] serdev: handle devices without an ACPI or device tree node ChunAn Wu
2026-10-24  2:29 ` [PATCH v4 1/3] " ChunAn Wu
2026-10-24  2:29 ` [PATCH v4] platform/x86: dell-uart-backlight: Bind through normal serdev matching ChunAn Wu
2026-10-24 11:59   ` kernel test robot
2026-10-24 12:03     ` Markus Probst [this message]
2026-10-24 17:42   ` kernel test robot
2026-10-24  2:29 ` [PATCH v4 3/3] platform/x86: lenovo-yoga-tab2-pro-1380-fastcharger: " ChunAn Wu
2026-10-24  3:50 ` [PATCH v4 2/3] platform/x86: dell-uart-backlight: " ChunAn Wu
2026-10-24  8:40 ` [PATCH v4 0/3] serdev: handle devices without an ACPI or device tree node An Wu
2026-10-24 11:48   ` Markus Probst

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=0197324d19f5c68e46dab41e22dbfc4c1bc34813.camel@posteo.de \
    --to=markus.probst@posteo.de \
    --cc=an.wu@canonical.com \
    --cc=derekjohn.clark@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hansg@kernel.org \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=jirislaby@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mpearson-lenovo@squebb.ca \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=platform-driver-x86@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®