From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [akpm-mm:mm-new 286/330] include/dup.h:354:25: error: stray '\302' in program
Date: Mon, 09 Mar 2026 00:53:17 +0100 [thread overview]
Message-ID: <202603090023.npem8cfw-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence bisect report"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
CC: David Hildenbrand <david@kernel.org>
TO: Anthony Yznaga <anthony.yznaga@oracle.com>
CC: Andrew Morton <akpm@linux-foundation.org>
CC: Linux Memory Management List <linux-mm@kvack.org>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-new
head: 167400fd4c51f9e5ea8fc9d33c89c938799be4be
commit: 84cd8de2b92a1ccf493c43da8b31bb983d320ca7 [286/330] mm-prevent-droppable-mappings-from-being-locked-fix
:::::: branch date: 2 hours ago
:::::: commit date: 2 hours ago
config: x86_64-allnoconfig-bpf (https://download.01.org/0day-ci/archive/20260309/202603090023.npem8cfw-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260309/202603090023.npem8cfw-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/r/202603090023.npem8cfw-lkp@intel.com/
All error/warnings (new ones prefixed by >>):
In file included from vma_internal.h:55,
from shared.h:11,
from main.c:3:
>> include/dup.h:354:9: warning: ISO C99 requires whitespace after the macro name
354 | #define VM_NO_MLOCK_MASK (VM_SPECIAL | VM_DROPPABLE)
| ^~~~~~~~~~~~~~~~
../../../mm/vma.c: In function '__mmap_complete':
>> include/dup.h:354:25: error: stray '\302' in program
354 | #define VM_NO_MLOCK_MASK<U+00A0> <U+00A0> <U+00A0> <U+00A0>(VM_SPECIAL | VM_DROPPABLE)
| ^~~~~~~~
../../../mm/vma.c:2592:33: note: in expansion of macro 'VM_NO_MLOCK_MASK'
2592 | if ((vm_flags & VM_NO_MLOCK_MASK) || vma_is_dax(vma) ||
| ^~~~~~~~~~~~~~~~
include/dup.h:354:27: error: stray '\302' in program
354 | #define VM_NO_MLOCK_MASK<U+00A0> <U+00A0> <U+00A0> <U+00A0>(VM_SPECIAL | VM_DROPPABLE)
| ^~~~~~~~
../../../mm/vma.c:2592:33: note: in expansion of macro 'VM_NO_MLOCK_MASK'
2592 | if ((vm_flags & VM_NO_MLOCK_MASK) || vma_is_dax(vma) ||
| ^~~~~~~~~~~~~~~~
include/dup.h:354:29: error: stray '\302' in program
354 | #define VM_NO_MLOCK_MASK<U+00A0> <U+00A0> <U+00A0> <U+00A0>(VM_SPECIAL | VM_DROPPABLE)
| ^~~~~~~~
../../../mm/vma.c:2592:33: note: in expansion of macro 'VM_NO_MLOCK_MASK'
2592 | if ((vm_flags & VM_NO_MLOCK_MASK) || vma_is_dax(vma) ||
| ^~~~~~~~~~~~~~~~
include/dup.h:354:31: error: stray '\302' in program
354 | #define VM_NO_MLOCK_MASK<U+00A0> <U+00A0> <U+00A0> <U+00A0>(VM_SPECIAL | VM_DROPPABLE)
| ^~~~~~~~
../../../mm/vma.c:2592:33: note: in expansion of macro 'VM_NO_MLOCK_MASK'
2592 | if ((vm_flags & VM_NO_MLOCK_MASK) || vma_is_dax(vma) ||
| ^~~~~~~~~~~~~~~~
--
In file included from vma_internal.h:55,
from shared.h:11,
from shared.c:3:
>> include/dup.h:354:9: warning: ISO C99 requires whitespace after the macro name
354 | #define VM_NO_MLOCK_MASK (VM_SPECIAL | VM_DROPPABLE)
| ^~~~~~~~~~~~~~~~
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-03-08 23:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-08 23:53 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-03-09 0:11 [akpm-mm:mm-new 286/330] include/dup.h:354:25: error: stray '\302' in program kernel test robot
2026-03-09 5:31 ` Andrew Morton
2026-03-09 6:27 ` anthony.yznaga
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=202603090023.npem8cfw-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@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.