From: kernel test robot <lkp@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [akpm-mm:master 1/1] htmldocs: arch/x86/entry/vdso/Makefile:7: lib/vdso/Makefile.include: No such file or directory
Date: Sun, 9 Mar 2025 15:41:40 +0800 [thread overview]
Message-ID: <202503091510.Q1KEoTrx-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git master
head: 38bcd10de11e3ae4b49e93a5bd12a490aafc6fed
commit: 38bcd10de11e3ae4b49e93a5bd12a490aafc6fed [1/1] foo
reproduce: (https://download.01.org/0day-ci/archive/20250309/202503091510.Q1KEoTrx-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/202503091510.Q1KEoTrx-lkp@intel.com/
All errors (new ones prefixed by >>):
>> arch/x86/entry/vdso/Makefile:7: lib/vdso/Makefile.include: No such file or directory
>> make[5]: *** No rule to make target 'lib/vdso/Makefile.include'.
arch/x86/entry/vdso/Makefile:7: Failed to remake makefile 'lib/vdso/Makefile.include'.
make[4]: *** [scripts/Makefile.clean:61: arch/x86/entry/vdso] Error 2
make[4]: Target '__clean' not remade because of errors.
make[3]: *** [scripts/Makefile.clean:61: arch/x86/entry] Error 2
make[3]: Target '__clean' not remade because of errors.
vim +7 arch/x86/entry/vdso/Makefile
5
6 # Include the generic Makefile to check the built vDSO:
> 7 include $(srctree)/lib/vdso/Makefile.include
8
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-03-09 7:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202503091510.Q1KEoTrx-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--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