From: Anshuman Khandual <anshuman.khandual@arm.com>
To: kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Dinh Nguyen <dinguyen@kernel.org>
Subject: Re: [dinguyen:set_fs-2 1/1] mm/mmap.c:105:9: error: '__P000' undeclared here (not in a function)
Date: Mon, 28 Feb 2022 08:20:38 +0530 [thread overview]
Message-ID: <efce0a6e-3560-716b-bfe4-586d87f40b1f@arm.com> (raw)
In-Reply-To: <202202260955.oz8w72wD-lkp@intel.com>
On 2/26/22 7:32 AM, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/dinguyen/linux.git set_fs-2
> head: 18dc1399170788b241181d48da03cf70a4139d5f
> commit: 18dc1399170788b241181d48da03cf70a4139d5f [1/1] nios2/mm: Enable ARCH_HAS_VM_GET_PAGE_PROT
> config: nios2-buildonly-randconfig-r001-20220226 (https://download.01.org/0day-ci/archive/20220226/202202260955.oz8w72wD-lkp@intel.com/config)
> compiler: nios2-linux-gcc (GCC) 11.2.0
> reproduce (this is a W=1 build):
> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> # https://git.kernel.org/pub/scm/linux/kernel/git/dinguyen/linux.git/commit/?id=18dc1399170788b241181d48da03cf70a4139d5f
> git remote add dinguyen https://git.kernel.org/pub/scm/linux/kernel/git/dinguyen/linux.git
> git fetch --no-tags dinguyen set_fs-2
> git checkout 18dc1399170788b241181d48da03cf70a4139d5f
> # save the config file to linux build tree
> mkdir build_dir
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=nios2 SHELL=/bin/bash
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
>
> All errors (new ones prefixed by >>):
>
>>> mm/mmap.c:105:9: error: '__P000' undeclared here (not in a function)
> 105 | __P000, __P001, __P010, __P011, __P100, __P101, __P110, __P111,
> | ^~~~~~
>>> mm/mmap.c:105:17: error: '__P001' undeclared here (not in a function)
> 105 | __P000, __P001, __P010, __P011, __P100, __P101, __P110, __P111,
> | ^~~~~~
>>> mm/mmap.c:105:25: error: '__P010' undeclared here (not in a function)
> 105 | __P000, __P001, __P010, __P011, __P100, __P101, __P110, __P111,
> | ^~~~~~
>>> mm/mmap.c:105:33: error: '__P011' undeclared here (not in a function)
> 105 | __P000, __P001, __P010, __P011, __P100, __P101, __P110, __P111,
> | ^~~~~~
>>> mm/mmap.c:105:41: error: '__P100' undeclared here (not in a function)
> 105 | __P000, __P001, __P010, __P011, __P100, __P101, __P110, __P111,
> | ^~~~~~
>>> mm/mmap.c:105:49: error: '__P101' undeclared here (not in a function)
> 105 | __P000, __P001, __P010, __P011, __P100, __P101, __P110, __P111,
> | ^~~~~~
>>> mm/mmap.c:105:57: error: '__P110' undeclared here (not in a function)
> 105 | __P000, __P001, __P010, __P011, __P100, __P101, __P110, __P111,
> | ^~~~~~
>>> mm/mmap.c:105:65: error: '__P111' undeclared here (not in a function)
> 105 | __P000, __P001, __P010, __P011, __P100, __P101, __P110, __P111,
> | ^~~~~~
>>> mm/mmap.c:106:9: error: '__S000' undeclared here (not in a function)
> 106 | __S000, __S001, __S010, __S011, __S100, __S101, __S110, __S111
> | ^~~~~~
>>> mm/mmap.c:106:17: error: '__S001' undeclared here (not in a function)
> 106 | __S000, __S001, __S010, __S011, __S100, __S101, __S110, __S111
> | ^~~~~~
>>> mm/mmap.c:106:25: error: '__S010' undeclared here (not in a function)
> 106 | __S000, __S001, __S010, __S011, __S100, __S101, __S110, __S111
> | ^~~~~~
>>> mm/mmap.c:106:33: error: '__S011' undeclared here (not in a function)
> 106 | __S000, __S001, __S010, __S011, __S100, __S101, __S110, __S111
> | ^~~~~~
>>> mm/mmap.c:106:41: error: '__S100' undeclared here (not in a function)
> 106 | __S000, __S001, __S010, __S011, __S100, __S101, __S110, __S111
> | ^~~~~~
>>> mm/mmap.c:106:49: error: '__S101' undeclared here (not in a function)
> 106 | __S000, __S001, __S010, __S011, __S100, __S101, __S110, __S111
> | ^~~~~~
>>> mm/mmap.c:106:57: error: '__S110' undeclared here (not in a function)
> 106 | __S000, __S001, __S010, __S011, __S100, __S101, __S110, __S111
> | ^~~~~~
>>> mm/mmap.c:106:65: error: '__S111' undeclared here (not in a function)
> 106 | __S000, __S001, __S010, __S011, __S100, __S101, __S110, __S111
> |
Seems like this tree might have just applied a single patch instead of the entire
series. The branch set_fs-2 does not seem to be present anymore and the commit ID
is not reachable from any other branch either, hence will ignore this report.
https://git.kernel.org/pub/scm/linux/kernel/git/dinguyen/linux.git/commit/?id=18dc1399170788b241181d48da03cf70a4139d5f
- Anshuman
prev parent reply other threads:[~2022-02-28 2:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-26 2:02 kernel test robot
2022-02-28 2:50 ` Anshuman Khandual [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=efce0a6e-3560-716b-bfe4-586d87f40b1f@arm.com \
--to=anshuman.khandual@arm.com \
--cc=dinguyen@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.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
all inboxes | Powered by JetHome®