From: kernel test robot <lkp@intel.com>
To: Ba Jing <bajing@cmss.chinamobile.com>, mporter@kernel.crashing.org
Cc: 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:53:57 +0800 [thread overview]
Message-ID: <202410201405.3xFH0Ws9-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: alpha-randconfig-r072-20241020 (https://download.01.org/0day-ci/archive/20241020/202410201405.3xFH0Ws9-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 13.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241020/202410201405.3xFH0Ws9-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/202410201405.3xFH0Ws9-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/rapidio/rio-access.c: In function '__rio_local_read_config_8':
>> drivers/rapidio/rio-access.c:29:13: error: 'RIO_8_BAD' undeclared (first use in this function)
29 | if (RIO_##size##_BAD) return RIO_BAD_SIZE; \
| ^~~~
drivers/rapidio/rio-access.c:52:1: note: in expansion of macro 'RIO_LOP_READ'
52 | RIO_LOP_READ(8, u8, 1)
| ^~~~~~~~~~~~
drivers/rapidio/rio-access.c:29:13: note: each undeclared identifier is reported only once for each function it appears in
29 | if (RIO_##size##_BAD) return RIO_BAD_SIZE; \
| ^~~~
drivers/rapidio/rio-access.c:52:1: note: in expansion of macro 'RIO_LOP_READ'
52 | RIO_LOP_READ(8, u8, 1)
| ^~~~~~~~~~~~
drivers/rapidio/rio-access.c: In function '__rio_local_read_config_16':
>> drivers/rapidio/rio-access.c:29:13: error: 'RIO_16_BAD' undeclared (first use in this function)
29 | if (RIO_##size##_BAD) return RIO_BAD_SIZE; \
| ^~~~
drivers/rapidio/rio-access.c:53:1: note: in expansion of macro 'RIO_LOP_READ'
53 | RIO_LOP_READ(16, u16, 2)
| ^~~~~~~~~~~~
drivers/rapidio/rio-access.c: In function '__rio_local_read_config_32':
>> drivers/rapidio/rio-access.c:29:13: error: 'RIO_32_BAD' undeclared (first use in this function)
29 | if (RIO_##size##_BAD) return RIO_BAD_SIZE; \
| ^~~~
drivers/rapidio/rio-access.c:54:1: note: in expansion of macro 'RIO_LOP_READ'
54 | RIO_LOP_READ(32, u32, 4)
| ^~~~~~~~~~~~
drivers/rapidio/rio-access.c: In function '__rio_local_write_config_8':
drivers/rapidio/rio-access.c:48:13: error: 'RIO_8_BAD' undeclared (first use in this function)
48 | if (RIO_##size##_BAD) return RIO_BAD_SIZE; \
| ^~~~
drivers/rapidio/rio-access.c:55:1: note: in expansion of macro 'RIO_LOP_WRITE'
55 | RIO_LOP_WRITE(8, u8, 1)
| ^~~~~~~~~~~~~
drivers/rapidio/rio-access.c: In function '__rio_local_write_config_16':
drivers/rapidio/rio-access.c:48:13: error: 'RIO_16_BAD' undeclared (first use in this function)
48 | if (RIO_##size##_BAD) return RIO_BAD_SIZE; \
| ^~~~
drivers/rapidio/rio-access.c:56:1: note: in expansion of macro 'RIO_LOP_WRITE'
56 | RIO_LOP_WRITE(16, u16, 2)
| ^~~~~~~~~~~~~
drivers/rapidio/rio-access.c: In function '__rio_local_write_config_32':
drivers/rapidio/rio-access.c:48:13: error: 'RIO_32_BAD' undeclared (first use in this function)
48 | if (RIO_##size##_BAD) return RIO_BAD_SIZE; \
| ^~~~
drivers/rapidio/rio-access.c:57:1: note: in expansion of macro 'RIO_LOP_WRITE'
57 | RIO_LOP_WRITE(32, u32, 4)
| ^~~~~~~~~~~~~
drivers/rapidio/rio-access.c: In function 'rio_mport_read_config_8':
drivers/rapidio/rio-access.c:81:13: error: 'RIO_8_BAD' undeclared (first use in this function); did you mean 'RIO_OP_READ'?
81 | if (RIO_##size##_BAD) return RIO_BAD_SIZE; \
| ^~~~
drivers/rapidio/rio-access.c:105:1: note: in expansion of macro 'RIO_OP_READ'
105 | RIO_OP_READ(8, u8, 1)
| ^~~~~~~~~~~
drivers/rapidio/rio-access.c: In function 'rio_mport_read_config_16':
drivers/rapidio/rio-access.c:81:13: error: 'RIO_16_BAD' undeclared (first use in this function)
81 | if (RIO_##size##_BAD) return RIO_BAD_SIZE; \
| ^~~~
drivers/rapidio/rio-access.c:106:1: note: in expansion of macro 'RIO_OP_READ'
106 | RIO_OP_READ(16, u16, 2)
| ^~~~~~~~~~~
drivers/rapidio/rio-access.c: In function 'rio_mport_read_config_32':
drivers/rapidio/rio-access.c:81:13: error: 'RIO_32_BAD' undeclared (first use in this function)
81 | if (RIO_##size##_BAD) return RIO_BAD_SIZE; \
| ^~~~
drivers/rapidio/rio-access.c:107:1: note: in expansion of macro 'RIO_OP_READ'
107 | RIO_OP_READ(32, u32, 4)
| ^~~~~~~~~~~
drivers/rapidio/rio-access.c: In function 'rio_mport_write_config_8':
drivers/rapidio/rio-access.c:100:13: error: 'RIO_8_BAD' undeclared (first use in this function); did you mean 'RIO_OP_READ'?
100 | if (RIO_##size##_BAD) return RIO_BAD_SIZE; \
| ^~~~
drivers/rapidio/rio-access.c:108:1: note: in expansion of macro 'RIO_OP_WRITE'
108 | RIO_OP_WRITE(8, u8, 1)
| ^~~~~~~~~~~~
drivers/rapidio/rio-access.c: In function 'rio_mport_write_config_16':
drivers/rapidio/rio-access.c:100:13: error: 'RIO_16_BAD' undeclared (first use in this function)
100 | if (RIO_##size##_BAD) return RIO_BAD_SIZE; \
| ^~~~
drivers/rapidio/rio-access.c:109:1: note: in expansion of macro 'RIO_OP_WRITE'
109 | RIO_OP_WRITE(16, u16, 2)
| ^~~~~~~~~~~~
drivers/rapidio/rio-access.c: In function 'rio_mport_write_config_32':
drivers/rapidio/rio-access.c:100:13: error: 'RIO_32_BAD' undeclared (first use in this function)
100 | if (RIO_##size##_BAD) return RIO_BAD_SIZE; \
| ^~~~
drivers/rapidio/rio-access.c:110:1: note: in expansion of macro 'RIO_OP_WRITE'
110 | RIO_OP_WRITE(32, u32, 4)
| ^~~~~~~~~~~~
vim +/RIO_8_BAD +29 drivers/rapidio/rio-access.c
bd7bca4335a555 Ben Dooks (Codethink 2019-12-04 13)
394b701ce4fbfd Matt Porter 2005-11-07 14 /**
394b701ce4fbfd Matt Porter 2005-11-07 15 * RIO_LOP_READ - Generate rio_local_read_config_* functions
394b701ce4fbfd Matt Porter 2005-11-07 16 * @size: Size of configuration space read (8, 16, 32 bits)
394b701ce4fbfd Matt Porter 2005-11-07 17 * @type: C type of value argument
394b701ce4fbfd Matt Porter 2005-11-07 18 * @len: Length of configuration space read (1, 2, 4 bytes)
394b701ce4fbfd Matt Porter 2005-11-07 19 *
394b701ce4fbfd Matt Porter 2005-11-07 20 * Generates rio_local_read_config_* functions used to access
394b701ce4fbfd Matt Porter 2005-11-07 21 * configuration space registers on the local device.
394b701ce4fbfd Matt Porter 2005-11-07 22 */
394b701ce4fbfd Matt Porter 2005-11-07 23 #define RIO_LOP_READ(size,type,len) \
394b701ce4fbfd Matt Porter 2005-11-07 24 int __rio_local_read_config_##size \
394b701ce4fbfd Matt Porter 2005-11-07 25 (struct rio_mport *mport, u32 offset, type *value) \
394b701ce4fbfd Matt Porter 2005-11-07 26 { \
394b701ce4fbfd Matt Porter 2005-11-07 27 int res; \
394b701ce4fbfd Matt Porter 2005-11-07 28 u32 data = 0; \
394b701ce4fbfd Matt Porter 2005-11-07 @29 if (RIO_##size##_BAD) return RIO_BAD_SIZE; \
ad1e9380b17add Zhang Wei 2008-04-18 30 res = mport->ops->lcread(mport, mport->id, offset, len, &data); \
394b701ce4fbfd Matt Porter 2005-11-07 31 *value = (type)data; \
394b701ce4fbfd Matt Porter 2005-11-07 32 return res; \
394b701ce4fbfd Matt Porter 2005-11-07 33 }
394b701ce4fbfd Matt Porter 2005-11-07 34
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2024-10-20 6:54 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
2024-10-20 6:53 ` 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=202410201405.3xFH0Ws9-lkp@intel.com \
--to=lkp@intel.com \
--cc=alex.bou9@gmail.com \
--cc=bajing@cmss.chinamobile.com \
--cc=linux-kernel@vger.kernel.org \
--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.