public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Rong Chen <rong.a.chen@intel.com>
Cc: Philip Li <philip.li@intel.com>,
	kernel test robot <lkp@intel.com>, x86-ml <x86@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [tip:x86/pti] BUILD SUCCESS WITH WARNING 767d46ab566dd489733666efe48732d523c8c332
Date: Mon, 12 Oct 2020 16:37:08 +0200	[thread overview]
Message-ID: <20201012143708.GD22829@zn.tnic> (raw)
In-Reply-To: <c06bc69c-e3f6-2902-5df7-15cf2c9ea9d7@intel.com>

On Mon, Oct 12, 2020 at 05:16:54PM +0800, Rong Chen wrote:
> We have added the reported links in the report, you can find it in the
> latest tip report:
> 
> [tip:master] BUILD REGRESSION 820e6f502f021417140bc8ee11f9c7be148ea844
> 
> tree/branch:https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git   master
> branch HEAD: 820e6f502f021417140bc8ee11f9c7be148ea844  Merge branch 'efi/core'
> 
> Error/Warning reports:
> 
> https://lore.kernel.org/lkml/202010112007.JDl1BSci-lkp@intel.com

Thanks, that link has all the info needed to reproduce AFAICT, as long
as you make sure to send it to a mailing list which gets archived by
lore.kernel.org - otherwise the redirection won't work.

Thx.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

      reply	other threads:[~2020-10-12 14:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-17  1:12 [tip:x86/pti] BUILD SUCCESS WITH WARNING 767d46ab566dd489733666efe48732d523c8c332 kernel test robot
2020-09-17  6:12 ` Borislav Petkov
     [not found]   ` <20200917073620.GA4946@intel.com>
2020-09-17  8:00     ` Borislav Petkov
2020-09-17 13:37       ` Philip Li
2020-10-12  9:16         ` Rong Chen
2020-10-12 14:37           ` 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=20201012143708.GD22829@zn.tnic \
    --to=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=philip.li@intel.com \
    --cc=rong.a.chen@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