From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [linux-next:master 4656/10546] make[2]: *** No rule to make target 'rustdoc'.
Date: Fri, 16 Jun 2023 16:07:41 +0800 [thread overview]
Message-ID: <202306161619.FPePncdP-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence bisect report"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
CC: Linux Memory Management List <linux-mm@kvack.org>
TO: Miguel Ojeda <ojeda@kernel.org>
CC: "Björn Roy Baron" <bjorn3_gh@protonmail.com>
CC: Gary Guo <gary@garyguo.net>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: f7efed9f38f886edb450041b82a6f15d663c98f8
commit: 3ed03f4da06ede71ac53cf25b9441a372e9f2487 [4656/10546] rust: upgrade to Rust 1.68.2
:::::: branch date: 3 hours ago
:::::: commit date: 2 weeks ago
config: x86_64-rhel-8.3-rust (https://download.01.org/0day-ci/archive/20230616/202306161619.FPePncdP-lkp@intel.com/config)
compiler: clang version 15.0.7 (https://github.com/llvm/llvm-project.git 8dfdcc7b7bf66834a761bd8de445840ef68e4d1a)
reproduce: (https://download.01.org/0day-ci/archive/20230616/202306161619.FPePncdP-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/r/202306161619.FPePncdP-lkp@intel.com/
All errors (new ones prefixed by >>):
>> make[2]: *** No rule to make target 'rustdoc'.
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-06-16 8:08 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=202306161619.FPePncdP-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.