public inbox for linux-staging@lists.linux.dev
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Samyak <samyak.bambole07@gmail.com>, marvin24@gmx.de
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	gregkh@linuxfoundation.org, ac100@lists.launchpad.net,
	linux-tegra@vger.kernel.org, linux-staging@lists.linux.dev,
	linux-kernel@vger.kernel.org,
	Samyak Bambole <samyak.bambole07@gmail.com>
Subject: Re: [PATCH] staging: nvec: Use kzalloc_obj instead of kzalloc
Date: Mon, 16 Feb 2026 10:50:31 +0800	[thread overview]
Message-ID: <202602161056.Elbb21hV-lkp@intel.com> (raw)
In-Reply-To: <20260215122913.104064-1-samyak.bambole07@gmail.com>

Hi Samyak,

kernel test robot noticed the following build errors:

[auto build test ERROR on staging/staging-testing]

url:    https://github.com/intel-lab-lkp/linux/commits/Samyak/staging-nvec-Use-kzalloc_obj-instead-of-kzalloc/20260215-203130
base:   staging/staging-testing
patch link:    https://lore.kernel.org/r/20260215122913.104064-1-samyak.bambole07%40gmail.com
patch subject: [PATCH] staging: nvec: Use kzalloc_obj instead of kzalloc
config: arm-defconfig (https://download.01.org/0day-ci/archive/20260216/202602161056.Elbb21hV-lkp@intel.com/config)
compiler: clang version 23.0.0git (https://github.com/llvm/llvm-project afd4df07ab0262482829d4410a6bae9f2809d37b)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260216/202602161056.Elbb21hV-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/202602161056.Elbb21hV-lkp@intel.com/

All errors (new ones prefixed by >>):

>> drivers/staging/nvec/nvec_ps2.c:105:12: error: call to undeclared function 'kzalloc_obj'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
     105 |         ser_dev = kzalloc_obj(*ser_dev, GFP_KERNEL);
         |                   ^
>> drivers/staging/nvec/nvec_ps2.c:105:10: error: incompatible integer to pointer conversion assigning to 'struct serio *' from 'int' [-Wint-conversion]
     105 |         ser_dev = kzalloc_obj(*ser_dev, GFP_KERNEL);
         |                 ^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   2 errors generated.


vim +/kzalloc_obj +105 drivers/staging/nvec/nvec_ps2.c

    99	
   100	static int nvec_mouse_probe(struct platform_device *pdev)
   101	{
   102		struct nvec_chip *nvec = dev_get_drvdata(pdev->dev.parent);
   103		struct serio *ser_dev;
   104	
 > 105		ser_dev = kzalloc_obj(*ser_dev, GFP_KERNEL);
   106		if (!ser_dev)
   107			return -ENOMEM;
   108	
   109		ser_dev->id.type = SERIO_8042;
   110		ser_dev->write = ps2_sendcommand;
   111		ser_dev->start = ps2_startstreaming;
   112		ser_dev->stop = ps2_stopstreaming;
   113	
   114		strscpy(ser_dev->name, "nvec mouse", sizeof(ser_dev->name));
   115		strscpy(ser_dev->phys, "nvec", sizeof(ser_dev->phys));
   116	
   117		ps2_dev.ser_dev = ser_dev;
   118		ps2_dev.notifier.notifier_call = nvec_ps2_notifier;
   119		ps2_dev.nvec = nvec;
   120		nvec_register_notifier(nvec, &ps2_dev.notifier, 0);
   121	
   122		serio_register_port(ser_dev);
   123	
   124		return 0;
   125	}
   126	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  reply	other threads:[~2026-02-16  2:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-15 12:29 [PATCH] staging: nvec: Use kzalloc_obj instead of kzalloc Samyak
2026-02-16  2:50 ` kernel test robot [this message]
2026-02-16  8:14 ` kernel test robot

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=202602161056.Elbb21hV-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=ac100@lists.launchpad.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=linux-tegra@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=marvin24@gmx.de \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=samyak.bambole07@gmail.com \
    /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