From: kernel test robot <lkp@intel.com>
To: Ba Jing <bajing@cmss.chinamobile.com>, mporter@kernel.crashing.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
alex.bou9@gmail.com, linux-kernel@vger.kernel.org,
Ba Jing <bajing@cmss.chinamobile.com>
Subject: Re: [PATCH] rapidio: rio-access: remove unused macros
Date: Sun, 20 Oct 2024 14:23:02 +0800 [thread overview]
Message-ID: <202410201348.MoFc4X0v-lkp@intel.com> (raw)
In-Reply-To: <20241015000207.5047-1-bajing@cmss.chinamobile.com>
Hi Ba,
kernel test robot noticed the following build errors:
[auto build test ERROR on linus/master]
[also build test ERROR on v6.12-rc3 next-20241018]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Ba-Jing/rapidio-rio-access-remove-unused-macros/20241017-152330
base: linus/master
patch link: https://lore.kernel.org/r/20241015000207.5047-1-bajing%40cmss.chinamobile.com
patch subject: [PATCH] rapidio: rio-access: remove unused macros
config: i386-buildonly-randconfig-002-20241020 (https://download.01.org/0day-ci/archive/20241020/202410201348.MoFc4X0v-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/20241020/202410201348.MoFc4X0v-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/202410201348.MoFc4X0v-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/rapidio/rio-access.c:52:1: error: use of undeclared identifier 'RIO_8_BAD'
52 | RIO_LOP_READ(8, u8, 1)
| ^
drivers/rapidio/rio-access.c:29:6: note: expanded from macro 'RIO_LOP_READ'
29 | if (RIO_##size##_BAD) return RIO_BAD_SIZE; \
| ^
<scratch space>:171:1: note: expanded from here
171 | RIO_8_BAD
| ^
>> drivers/rapidio/rio-access.c:53:1: error: use of undeclared identifier 'RIO_16_BAD'
53 | RIO_LOP_READ(16, u16, 2)
| ^
drivers/rapidio/rio-access.c:29:6: note: expanded from macro 'RIO_LOP_READ'
29 | if (RIO_##size##_BAD) return RIO_BAD_SIZE; \
| ^
<scratch space>:174:1: note: expanded from here
174 | RIO_16_BAD
| ^
>> drivers/rapidio/rio-access.c:54:1: error: use of undeclared identifier 'RIO_32_BAD'
54 | RIO_LOP_READ(32, u32, 4)
| ^
drivers/rapidio/rio-access.c:29:6: note: expanded from macro 'RIO_LOP_READ'
29 | if (RIO_##size##_BAD) return RIO_BAD_SIZE; \
| ^
<scratch space>:177:1: note: expanded from here
177 | RIO_32_BAD
| ^
drivers/rapidio/rio-access.c:55:1: error: use of undeclared identifier 'RIO_8_BAD'
55 | RIO_LOP_WRITE(8, u8, 1)
| ^
drivers/rapidio/rio-access.c:48:6: note: expanded from macro 'RIO_LOP_WRITE'
48 | if (RIO_##size##_BAD) return RIO_BAD_SIZE; \
| ^
<scratch space>:180:1: note: expanded from here
180 | RIO_8_BAD
| ^
drivers/rapidio/rio-access.c:56:1: error: use of undeclared identifier 'RIO_16_BAD'
56 | RIO_LOP_WRITE(16, u16, 2)
| ^
drivers/rapidio/rio-access.c:48:6: note: expanded from macro 'RIO_LOP_WRITE'
48 | if (RIO_##size##_BAD) return RIO_BAD_SIZE; \
| ^
<scratch space>:183:1: note: expanded from here
183 | RIO_16_BAD
| ^
drivers/rapidio/rio-access.c:57:1: error: use of undeclared identifier 'RIO_32_BAD'
57 | RIO_LOP_WRITE(32, u32, 4)
| ^
drivers/rapidio/rio-access.c:48:6: note: expanded from macro 'RIO_LOP_WRITE'
48 | if (RIO_##size##_BAD) return RIO_BAD_SIZE; \
| ^
<scratch space>:186:1: note: expanded from here
186 | RIO_32_BAD
| ^
drivers/rapidio/rio-access.c:105:1: error: use of undeclared identifier 'RIO_8_BAD'
105 | RIO_OP_READ(8, u8, 1)
| ^
drivers/rapidio/rio-access.c:81:6: note: expanded from macro 'RIO_OP_READ'
81 | if (RIO_##size##_BAD) return RIO_BAD_SIZE; \
| ^
<scratch space>:25:1: note: expanded from here
25 | RIO_8_BAD
| ^
drivers/rapidio/rio-access.c:106:1: error: use of undeclared identifier 'RIO_16_BAD'
106 | RIO_OP_READ(16, u16, 2)
| ^
drivers/rapidio/rio-access.c:81:6: note: expanded from macro 'RIO_OP_READ'
81 | if (RIO_##size##_BAD) return RIO_BAD_SIZE; \
| ^
<scratch space>:28:1: note: expanded from here
28 | RIO_16_BAD
| ^
drivers/rapidio/rio-access.c:107:1: error: use of undeclared identifier 'RIO_32_BAD'
107 | RIO_OP_READ(32, u32, 4)
| ^
drivers/rapidio/rio-access.c:81:6: note: expanded from macro 'RIO_OP_READ'
81 | if (RIO_##size##_BAD) return RIO_BAD_SIZE; \
| ^
<scratch space>:31:1: note: expanded from here
31 | RIO_32_BAD
| ^
drivers/rapidio/rio-access.c:108:1: error: use of undeclared identifier 'RIO_8_BAD'
108 | RIO_OP_WRITE(8, u8, 1)
| ^
drivers/rapidio/rio-access.c:100:6: note: expanded from macro 'RIO_OP_WRITE'
100 | if (RIO_##size##_BAD) return RIO_BAD_SIZE; \
| ^
<scratch space>:34:1: note: expanded from here
34 | RIO_8_BAD
| ^
drivers/rapidio/rio-access.c:109:1: error: use of undeclared identifier 'RIO_16_BAD'
109 | RIO_OP_WRITE(16, u16, 2)
| ^
drivers/rapidio/rio-access.c:100:6: note: expanded from macro 'RIO_OP_WRITE'
100 | if (RIO_##size##_BAD) return RIO_BAD_SIZE; \
| ^
<scratch space>:37:1: note: expanded from here
37 | RIO_16_BAD
| ^
drivers/rapidio/rio-access.c:110:1: error: use of undeclared identifier 'RIO_32_BAD'
110 | RIO_OP_WRITE(32, u32, 4)
| ^
drivers/rapidio/rio-access.c:100:6: note: expanded from macro 'RIO_OP_WRITE'
100 | if (RIO_##size##_BAD) return RIO_BAD_SIZE; \
| ^
<scratch space>:40:1: note: expanded from here
40 | RIO_32_BAD
| ^
12 errors generated.
vim +/RIO_8_BAD +52 drivers/rapidio/rio-access.c
394b701ce4fbfd Matt Porter 2005-11-07 51
394b701ce4fbfd Matt Porter 2005-11-07 @52 RIO_LOP_READ(8, u8, 1)
394b701ce4fbfd Matt Porter 2005-11-07 @53 RIO_LOP_READ(16, u16, 2)
394b701ce4fbfd Matt Porter 2005-11-07 @54 RIO_LOP_READ(32, u32, 4)
394b701ce4fbfd Matt Porter 2005-11-07 55 RIO_LOP_WRITE(8, u8, 1)
394b701ce4fbfd Matt Porter 2005-11-07 56 RIO_LOP_WRITE(16, u16, 2)
394b701ce4fbfd Matt Porter 2005-11-07 57 RIO_LOP_WRITE(32, u32, 4)
394b701ce4fbfd Matt Porter 2005-11-07 58
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-10-20 6:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 0:02 [PATCH] rapidio: rio-access: remove unused macros Ba Jing
2024-10-20 6:23 ` kernel test robot [this message]
2024-10-20 6:53 ` 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=202410201348.MoFc4X0v-lkp@intel.com \
--to=lkp@intel.com \
--cc=alex.bou9@gmail.com \
--cc=bajing@cmss.chinamobile.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mporter@kernel.crashing.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 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.