linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: kernel test robot <lkp@intel.com>
Cc: Anthony Yznaga <anthony.yznaga@oracle.com>,
	<oe-kbuild-all@lists.linux.dev>,
	David Hildenbrand <david@kernel.org>,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [akpm-mm:mm-new 286/330] include/dup.h:354:25: error: stray '\302' in program
Date: Sun, 8 Mar 2026 22:31:52 -0700	[thread overview]
Message-ID: <20260308223152.7c99aaa3c73f819b7844fa07@linux-foundation.org> (raw)
In-Reply-To: <aa4QKbYOvGmDEqVG@rli9-mobl>

On Mon, 9 Mar 2026 08:11:21 +0800 kernel test robot <lkp@intel.com> wrote:

> 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
> 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)
>          |         ^~~~~~~~~~~~~~~~

bah, OK, my attempt to turn the incoming email into something usable
didn't work out,  Let me attempt to repair that.

Anthony, text/plain changelogged, signed-off patches are very much
preferred, thanks.



  reply	other threads:[~2026-03-09  5:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-09  0:11 kernel test robot
2026-03-09  5:31 ` Andrew Morton [this message]
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=20260308223152.7c99aaa3c73f819b7844fa07@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=anthony.yznaga@oracle.com \
    --cc=david@kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --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