public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Johannes Berg <johannes.berg@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
	Gregory Greenman <gregory.greenman@intel.com>
Subject: drivers/net/wireless/intel/iwlwifi/pcie/trans.c:1093:9: warning: 'CAUSE' redefined
Date: Sun, 15 Mar 2026 12:55:58 +0800	[thread overview]
Message-ID: <202603151235.VjEiAR0o-lkp@intel.com> (raw)

Hi Johannes,

FYI, the error/warning still remains.

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   80234b5ab240f52fa45d201e899e207b9265ef91
commit: c1918196427b917d1fbf064b07538410807f8b03 iwlwifi: pcie: simplify MSI-X cause mapping
date:   3 years, 10 months ago
config: mips-allyesconfig (https://download.01.org/0day-ci/archive/20260315/202603151235.VjEiAR0o-lkp@intel.com/config)
compiler: mips-linux-gcc (GCC) 15.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260315/202603151235.VjEiAR0o-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/202603151235.VjEiAR0o-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/net/wireless/intel/iwlwifi/pcie/trans.c:1093:9: warning: 'CAUSE' redefined
    1093 | #define CAUSE(reg, mask)                                                \
         |         ^~~~~
   In file included from arch/mips/include/asm/ptrace.h:19,
                    from include/linux/sched/signal.h:14,
                    from include/linux/rcuwait.h:6,
                    from include/linux/percpu-rwsem.h:7,
                    from include/linux/fs.h:33,
                    from arch/mips/include/asm/elf.h:12,
                    from include/linux/elf.h:6,
                    from include/linux/module.h:19,
                    from include/linux/device/driver.h:21,
                    from include/linux/device.h:32,
                    from include/linux/pci.h:37,
                    from drivers/net/wireless/intel/iwlwifi/pcie/trans.c:7:
   arch/mips/include/uapi/asm/ptrace.h:18:9: note: this is the location of the previous definition
      18 | #define CAUSE           65
         |         ^~~~~


vim +/CAUSE +1093 drivers/net/wireless/intel/iwlwifi/pcie/trans.c

  1092	
> 1093	#define CAUSE(reg, mask)						\
  1094		{								\
  1095			.mask_reg = reg,					\
  1096			.bit = ilog2(mask),					\
  1097			.addr = ilog2(mask) +					\
  1098				((reg) == CSR_MSIX_FH_INT_MASK_AD ? -16 :	\
  1099				 (reg) == CSR_MSIX_HW_INT_MASK_AD ? 16 :	\
  1100				 0xffff),	/* causes overflow warning */	\
  1101		}
  1102	

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

             reply	other threads:[~2026-03-15  4:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-15  4:55 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-05-03 19:30 drivers/net/wireless/intel/iwlwifi/pcie/trans.c:1093:9: warning: 'CAUSE' redefined 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=202603151235.VjEiAR0o-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=gregory.greenman@intel.com \
    --cc=johannes.berg@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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