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 f15a0a732aefb46f999c2a8aa8f9f16e71cec5b2
Date: Fri, 19 Mar 2021 11:32:51 +0100 [thread overview]
Message-ID: <20210319103251.GD6251@zn.tnic> (raw)
In-Reply-To: <60547c67.LV3ZdWGiJYWHhzsC%lkp@intel.com>
On Fri, Mar 19, 2021 at 06:26:47PM +0800, kernel test robot wrote:
> tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/seves
> branch HEAD: f15a0a732aefb46f999c2a8aa8f9f16e71cec5b2 x86/sev-es: Replace open-coded hlt-loops with sev_es_terminate()
>
> possible Warning in current branch:
>
> arch/x86/kernel/sev-es.c:1377 safe_stack_exc_vmm_communication() warn: ignoring unreachable code.
That's probably something you trigger with clang-13 but I don't have
that report in my mbox.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
prev parent reply other threads:[~2021-03-19 10:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 10:26 [tip:x86/seves] BUILD SUCCESS WITH WARNING f15a0a732aefb46f999c2a8aa8f9f16e71cec5b2 kernel test robot
2021-03-19 10:32 ` Borislav Petkov [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=20210319103251.GD6251@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