From: kernel test robot <lkp@intel.com>
To: Muhammad Usama Anjum <usama.anjum@collabora.com>
Cc: oe-kbuild-all@lists.linux.dev,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [akpm-mm:mm-unstable 75/86] hugepage-vmemmap.c:141:26: error: 'MAP_LENGTH' undeclared
Date: Wed, 17 Jan 2024 00:00:21 +0800 [thread overview]
Message-ID: <202401162313.K6z6Sf6q-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-unstable
head: 0665259690a91b4df83cc10b92118ee35512369c
commit: f5f6467271ba989cc602a8160e08eadd45611ea9 [75/86] selftests/mm: hugepage-vmemmap: conform test to TAP format output
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240116/202401162313.K6z6Sf6q-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/202401162313.K6z6Sf6q-lkp@intel.com/
All errors (new ones prefixed by >>):
hugepage-vmemmap.c: In function 'main':
>> hugepage-vmemmap.c:141:26: error: 'MAP_LENGTH' undeclared (first use in this function)
141 | if (munmap(addr, MAP_LENGTH))
| ^~~~~~~~~~
hugepage-vmemmap.c:141:26: note: each undeclared identifier is reported only once for each function it appears in
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-01-16 16:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 16:00 kernel test robot [this message]
2024-01-17 4:36 ` Muhammad Usama Anjum
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=202401162313.K6z6Sf6q-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=usama.anjum@collabora.com \
/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