From: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>
To: lkp <lkp@intel.com>
Cc: "Yu, Yu-cheng" <yu-cheng.yu@intel.com>,
"oe-kbuild-all@lists.linux.dev" <oe-kbuild-all@lists.linux.dev>,
"bp@alien8.de" <bp@alien8.de>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"keescook@chromium.org" <keescook@chromium.org>,
"x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>
Subject: Re: [tip:x86/shstk 6/42] htmldocs: Warning: arch/x86/Kconfig references a file that doesn't exist: Documentation/x86/shstk.rst
Date: Fri, 28 Jul 2023 23:25:51 +0000 [thread overview]
Message-ID: <4bb0b480c0bc514dd9e6472ab420b3da51011beb.camel@intel.com> (raw)
In-Reply-To: <202307271956.IxoG9X0c-lkp@intel.com>
On Thu, 2023-07-27 at 19:55 +0800, kernel test robot wrote:
> tree:
> https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/shstk
> head: c19a153cc0b172c8e1869d6dee52f6aadd73d3c4
> commit: 18e66b695e787374ca762ecdeaa1ab5e3772af94 [6/42] x86/shstk:
> Add Kconfig option for shadow stack
> reproduce:
> (https://download.01.org/0day-ci/archive/20230727/202307271956.IxoG9X
> 0c-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/202307271956.IxoG9X0c-lkp@intel.com/
>
> All warnings (new ones prefixed by >>):
>
> > > Warning: arch/x86/Kconfig references a file that doesn't exist:
> > > Documentation/x86/shstk.rst
Looks like the x86 documentation moved, and it just needs this:
diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
index e860f805199f..99e7552fff4f 100644
--- a/arch/x86/Kconfig
+++ b/arch/x86/Kconfig
@@ -1969,7 +1969,7 @@ config X86_USER_SHADOW_STACK
CPUs supporting shadow stacks were first released in 2020.
- See Documentation/x86/shstk.rst for more information.
+ See Documentation/arch/x86/shstk.rst for more information.
If unsure, say N.
Dave, would you like a proper patch for it?
prev parent reply other threads:[~2023-07-28 23:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 11:55 kernel test robot
2023-07-28 23:25 ` Edgecombe, Rick P [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=4bb0b480c0bc514dd9e6472ab420b3da51011beb.camel@intel.com \
--to=rick.p.edgecombe@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=x86@kernel.org \
--cc=yu-cheng.yu@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®