From: kernel test robot <lkp@intel.com>
To: Marcos Paulo de Souza <mpdesouza@suse.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Shuah Khan <skhan@linuxfoundation.org>,
Joe Lawrence <joe.lawrence@redhat.com>,
Petr Mladek <pmladek@suse.com>
Subject: [linux-next:master 1016/2825] make[2]: *** kselftest/livepatch/test_modules: No such file or directory. Stop.
Date: Tue, 30 Jan 2024 07:08:47 +0800 [thread overview]
Message-ID: <202401300736.GkSZoSrA-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 596764183be8ebb13352b281a442a1f1151c9b06
commit: c4bbe83d27c2446a033cc0381c3fb6be5e8c41c7 [1016/2825] livepatch: Move tests from lib/livepatch to selftests/livepatch
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/20240130/202401300736.GkSZoSrA-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/202401300736.GkSZoSrA-lkp@intel.com/
All errors (new ones prefixed by >>):
>> make[2]: *** kselftest/livepatch/test_modules: No such file or directory. Stop.
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-01-29 23:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 23:08 kernel test robot [this message]
2024-01-30 14:39 ` [linux-next:master 1016/2825] make[2]: *** kselftest/livepatch/test_modules: No such file or directory. Stop Marcos Paulo de Souza
2024-01-31 15:34 ` Petr Mladek
2024-01-31 18:39 ` Marcos Paulo de Souza
2024-01-31 18:40 ` Marcos Paulo de Souza
2024-02-05 18:05 ` Marcos Paulo de Souza
2024-02-14 14:27 ` Marcos Paulo de Souza
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=202401300736.GkSZoSrA-lkp@intel.com \
--to=lkp@intel.com \
--cc=joe.lawrence@redhat.com \
--cc=linux-mm@kvack.org \
--cc=mpdesouza@suse.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pmladek@suse.com \
--cc=skhan@linuxfoundation.org \
/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;
as well as URLs for NNTP newsgroup(s).