Linux kernel staging patches
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Balakrishnan Sambath <balakrishnan.s@microchip.com>,
	Marc Dietrich <marvin24@gmx.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Stephen Warren <swarren@nvidia.com>,
	Prashant Gaikwad <pgaikwad@nvidia.com>
Cc: oe-kbuild-all@lists.linux.dev, ac100@lists.launchpad.net,
	linux-tegra@vger.kernel.org, linux-staging@lists.linux.dev,
	linux-kernel@vger.kernel.org,
	Balakrishnan Sambath <balakrishnan.s@microchip.com>
Subject: Re: [PATCH] staging: nvec: disable i2c slave on remove
Date: Fri, 3 Jul 2026 05:13:47 +0800	[thread overview]
Message-ID: <202607030502.TdzG5XDE-lkp@intel.com> (raw)
In-Reply-To: <20260702-contrib-nvec-clk-leak-v1-1-659bcbe74e56@microchip.com>

Hi Balakrishnan,

kernel test robot noticed the following build errors:

[auto build test ERROR on be5c93fa674f0fc3c8f359c2143abce6bbb422e6]

url:    https://github.com/intel-lab-lkp/linux/commits/Balakrishnan-Sambath/staging-nvec-disable-i2c-slave-on-remove/20260702-185025
base:   be5c93fa674f0fc3c8f359c2143abce6bbb422e6
patch link:    https://lore.kernel.org/r/20260702-contrib-nvec-clk-leak-v1-1-659bcbe74e56%40microchip.com
patch subject: [PATCH] staging: nvec: disable i2c slave on remove
config: arm64-randconfig-002-20260702 (https://download.01.org/0day-ci/archive/20260703/202607030502.TdzG5XDE-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 8.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260703/202607030502.TdzG5XDE-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/202607030502.TdzG5XDE-lkp@intel.com/

All errors (new ones prefixed by >>):

   drivers/staging/nvec/nvec.c: In function 'tegra_nvec_remove':
>> drivers/staging/nvec/nvec.c:911:2: error: implicit declaration of function 'nvec_disable_i2c_slave'; did you mean 'disable_irq_wake'? [-Werror=implicit-function-declaration]
     nvec_disable_i2c_slave(nvec);
     ^~~~~~~~~~~~~~~~~~~~~~
     disable_irq_wake
   cc1: some warnings being treated as errors


vim +911 drivers/staging/nvec/nvec.c

   899	
   900	static void tegra_nvec_remove(struct platform_device *pdev)
   901	{
   902		struct nvec_chip *nvec = platform_get_drvdata(pdev);
   903	
   904		nvec_toggle_global_events(nvec, false);
   905		mfd_remove_devices(nvec->dev);
   906		nvec_unregister_notifier(nvec, &nvec->nvec_status_notifier);
   907		cancel_work_sync(&nvec->rx_work);
   908		cancel_work_sync(&nvec->tx_work);
   909		if (pm_power_off == nvec_power_off)
   910			pm_power_off = NULL;
 > 911		nvec_disable_i2c_slave(nvec);
   912	}
   913	

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

      reply	other threads:[~2026-07-02 21:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-02 10:36 [PATCH] staging: nvec: disable i2c slave on remove Balakrishnan Sambath
2026-07-02 21:13 ` kernel test robot [this message]

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=202607030502.TdzG5XDE-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=ac100@lists.launchpad.net \
    --cc=balakrishnan.s@microchip.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=linux-tegra@vger.kernel.org \
    --cc=marvin24@gmx.de \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=pgaikwad@nvidia.com \
    --cc=swarren@nvidia.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