From: Muhammad Usama Anjum <usama.anjum@collabora.com>
To: kernel test robot <lkp@intel.com>
Cc: Muhammad Usama Anjum <usama.anjum@collabora.com>,
oe-kbuild-all@lists.linux.dev,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [akpm-mm:mm-unstable 75/86] hugepage-vmemmap.c:141:26: error: 'MAP_LENGTH' undeclared
Date: Wed, 17 Jan 2024 09:36:58 +0500 [thread overview]
Message-ID: <2252609d-2685-46c2-987c-47686671d25b@collabora.com> (raw)
In-Reply-To: <202401162313.K6z6Sf6q-lkp@intel.com>
This has already been fixed by 00bcfcd47a52 ("selftests: mm:
hugepage-vmemmap fails on 64K page size systems")
On 1/16/24 9:00 PM, kernel test robot wrote:
> 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
>
--
BR,
Muhammad Usama Anjum
prev parent reply other threads:[~2024-01-17 4:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 16:00 kernel test robot
2024-01-17 4:36 ` Muhammad Usama Anjum [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=2252609d-2685-46c2-987c-47686671d25b@collabora.com \
--to=usama.anjum@collabora.com \
--cc=akpm@linux-foundation.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