public inbox for linux-staging@lists.linux.dev
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Dima Volkovsk <s0ldw3ll@gmail.com>,
	marvin24@gmx.de, gregkh@linuxfoundation.org,
	ac100@lists.launchpad.net, linux-tegra@vger.kernel.org,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	Dima Volkovsk <s0ldw3ll@gmail.com>
Subject: Re: [PATCH] Staging: nvec: Fix pm_power_off reset condition in tegra_nvec_remove
Date: Mon, 10 Feb 2025 20:31:43 +0800	[thread overview]
Message-ID: <202502102056.z2poG8tW-lkp@intel.com> (raw)
In-Reply-To: <20250209201752.66313-1-s0ldw3ll@gmail.com>

Hi Dima,

kernel test robot noticed the following build warnings:

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

url:    https://github.com/intel-lab-lkp/linux/commits/Dima-Volkovsk/Staging-nvec-Fix-pm_power_off-reset-condition-in-tegra_nvec_remove/20250210-041929
base:   staging/staging-testing
patch link:    https://lore.kernel.org/r/20250209201752.66313-1-s0ldw3ll%40gmail.com
patch subject: [PATCH] Staging: nvec: Fix pm_power_off reset condition in tegra_nvec_remove
config: arm-defconfig (https://download.01.org/0day-ci/archive/20250210/202502102056.z2poG8tW-lkp@intel.com/config)
compiler: clang version 21.0.0git (https://github.com/llvm/llvm-project 6807164500e9920638e2ab0cdb4bf8321d24f8eb)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250210/202502102056.z2poG8tW-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/202502102056.z2poG8tW-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/staging/nvec/nvec.c:908:19: warning: using the result of an assignment as a condition without parentheses [-Wparentheses]
     908 |         if (pm_power_off = nvec_power_off)
         |             ~~~~~~~~~~~~~^~~~~~~~~~~~~~~~
   drivers/staging/nvec/nvec.c:908:19: note: place parentheses around the assignment to silence this warning
     908 |         if (pm_power_off = nvec_power_off)
         |                          ^               
         |             (                            )
   drivers/staging/nvec/nvec.c:908:19: note: use '==' to turn this assignment into an equality comparison
     908 |         if (pm_power_off = nvec_power_off)
         |                          ^
         |                          ==
   1 warning generated.


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

   896	
   897	static void tegra_nvec_remove(struct platform_device *pdev)
   898	{
   899		struct nvec_chip *nvec = platform_get_drvdata(pdev);
   900	
   901		nvec_toggle_global_events(nvec, false);
   902		mfd_remove_devices(nvec->dev);
   903		nvec_unregister_notifier(nvec, &nvec->nvec_status_notifier);
   904		cancel_work_sync(&nvec->rx_work);
   905		cancel_work_sync(&nvec->tx_work);
   906	
   907		/* only reset pm_power_off if it's our handler */
 > 908		if (pm_power_off = nvec_power_off)
   909			pm_power_off = NULL;
   910	}
   911	

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

  parent reply	other threads:[~2025-02-10 12:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-09 20:16 [PATCH] Staging: nvec: Fix pm_power_off reset condition in tegra_nvec_remove Dima Volkovsk
2025-02-10  6:10 ` Greg KH
2025-02-10 12:31 ` kernel test robot [this message]
2025-02-10 14:08 ` kernel test robot
2025-02-12  7:33 ` Dan Carpenter

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=202502102056.z2poG8tW-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=s0ldw3ll@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