From: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, vigneshr@ti.com, nm@ti.com,
Udit Kumar <u-kumar1@ti.com>
Subject: [ti:ti-linux-6.6.y-wip 44/137] drivers/net/can/m_can/m_can.c:1919:60: sparse: sparse: dubious: !x & y
Date: Thu, 10 Oct 2024 01:58:05 +0800 [thread overview]
Message-ID: <202410100112.hAuhC3pA-lkp@intel.com> (raw)
tree: git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git ti-linux-6.6.y-wip
head: 7866eaeb3c1ddb52b976c3e4140cdfbba28a74f3
commit: a09b9245edfe4d1ebb54e1b9cfe06a801fc4e972 [44/137] can: m_can: Map WoL to device_set_wakeup_enable
config: i386-randconfig-061-20241009 (https://download.01.org/0day-ci/archive/20241010/202410100112.hAuhC3pA-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241010/202410100112.hAuhC3pA-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/202410100112.hAuhC3pA-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/net/can/m_can/m_can.c:1919:60: sparse: sparse: dubious: !x & y
vim +1919 drivers/net/can/m_can/m_can.c
1911
1912 static int m_can_set_wol(struct net_device *dev, struct ethtool_wolinfo *wol)
1913 {
1914 struct m_can_classdev *cdev = netdev_priv(dev);
1915
1916 if ((wol->wolopts & WAKE_PHY) != wol->wolopts)
1917 return -EINVAL;
1918
> 1919 device_set_wakeup_enable(cdev->dev, !!wol->wolopts & WAKE_PHY);
1920
1921 return 0;
1922 }
1923
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-10-09 17:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202410100112.hAuhC3pA-lkp@intel.com \
--to=lkp@intel.com \
--cc=nm@ti.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=u-kumar1@ti.com \
--cc=vigneshr@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.