From: kernel test robot <lkp@intel.com>
To: Alexander Lobakin <aleksander.lobakin@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [alobakin:pfcp 8/8] lib/test_bitmap.c:1338:8: error: macro name missing
Date: Thu, 7 Sep 2023 23:37:40 +0800 [thread overview]
Message-ID: <202309072308.M6dIWWio-lkp@intel.com> (raw)
tree: https://github.com/alobakin/linux pfcp
head: 6f8d41d95df8ebab344c5c6ec0e364a30860068f
commit: 6f8d41d95df8ebab344c5c6ec0e364a30860068f [8/8] lib/bitmap: add tests for IP tunnel flags conversion helpers
config: arm64-randconfig-r005-20230907 (https://download.01.org/0day-ci/archive/20230907/202309072308.M6dIWWio-lkp@intel.com/config)
compiler: clang version 17.0.0 (https://github.com/llvm/llvm-project.git 4a5ac14ee968ff0ad5d2cc1ffa0299048db4c88a)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230907/202309072308.M6dIWWio-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/202309072308.M6dIWWio-lkp@intel.com/
All errors (new ones prefixed by >>):
>> lib/test_bitmap.c:1338:8: error: macro name missing
1338 | #define
| ^
1 error generated.
vim +1338 lib/test_bitmap.c
1328
1329 /*
1330 * Due to the previous flags design limitation, setting either
1331 * ``IP_TUNNEL_CSUM_BIT`` (on Big Endian) or ``IP_TUNNEL_DONT_FRAGMENT_BIT``
1332 * (on Little) also sets VTI/ISATAP bit. In the bitmap implementation, they
1333 * correspond to ``BIT(16)``, which is bigger than ``U16_MAX``, but still is
1334 * backward-compatible.
1335 */
1336 #ifdef __BIG_ENDIAN
1337 #define IP_TUNNEL_CONFLICT_BIT IP_TUNNEL_CSUM_BIT
> 1338 #define
1339 #else
1340 #define IP_TUNNEL_CONFLICT_BIT IP_TUNNEL_DONT_FRAGMENT_BIT
1341 #endif
1342
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-09-07 15:38 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=202309072308.M6dIWWio-lkp@intel.com \
--to=lkp@intel.com \
--cc=aleksander.lobakin@intel.com \
--cc=llvm@lists.linux.dev \
--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