From: Borislav Petkov <bp@alien8.de>
To: kernel test robot <lkp@intel.com>
Cc: x86-ml <x86@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: [tip:x86/seves] BUILD SUCCESS WITH WARNING f5ed777586e08e09c4b6f1e87161a145ee1431cf
Date: Fri, 11 Sep 2020 16:06:33 +0200 [thread overview]
Message-ID: <20200911140633.GB8472@zn.tnic> (raw)
In-Reply-To: <5f5b3f27.qfbP2yqzLurGC9yI%lkp@intel.com>
On Fri, Sep 11, 2020 at 05:11:03PM +0800, kernel test robot wrote:
> tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/seves
> branch HEAD: f5ed777586e08e09c4b6f1e87161a145ee1431cf x86/sev-es: Check required CPU features for SEV-ES
>
> Warning in current branch:
>
> arch/x86/kernel/sev-es.o: warning: objtool: safe_stack_exc_vmm_communication()+0x209: unreachable instruction
>
> Warning ids grouped by kconfigs:
>
> clang_recent_errors
> `-- x86_64-randconfig-a004-20200911
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Where do I get that randconfig from?
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
parent reply other threads:[~2020-09-11 15:43 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <5f5b3f27.qfbP2yqzLurGC9yI%lkp@intel.com>]
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=20200911140633.GB8472@zn.tnic \
--to=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=x86@kernel.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).