From: Philip Li <philip.li@intel.com>
To: Borislav Petkov <bp@alien8.de>
Cc: kernel test robot <lkp@intel.com>,
Rong Chen <rong.a.chen@intel.com>, x86-ml <x86@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [tip:x86/pti] BUILD SUCCESS WITH WARNING 767d46ab566dd489733666efe48732d523c8c332
Date: Thu, 17 Sep 2020 21:37:22 +0800 [thread overview]
Message-ID: <20200917133722.GA21986@intel.com> (raw)
In-Reply-To: <20200917080044.GD31960@zn.tnic>
On Thu, Sep 17, 2020 at 10:00:44AM +0200, Borislav Petkov wrote:
> On Thu, Sep 17, 2020 at 03:36:20PM +0800, Philip Li wrote:
> > The 2nd type is this one, which is a summarized report of head
> > to provide an overview. Most of time, repo owner can receive the
> > bisected mail. For this time, the issue is reported against peterz-queue
> > repo which has this 767d46ab56 head firstly. Since the head later appears
> > in tip, we just gather all issues and send the summary to tip related
> > recipients. But no more bisected mail.
>
> Yeah, but that second report is not very helpful because nowhere it says
> it is a summary and nowhere it has that link you pasted above so that
> some other maintainer can go look.
>
> Always put yourself in the recipient's shoes and ask yourself: "what can
> the recipient do with this report and does it have everything in there
> required to be able to reproduce the issue?"
>
> If not, then it needs changing.
thanks for the advice. We will provide update in 1-2 weeks for the progress
to make the report more informative and useful.
>
> > We will consider how to show useful produce info in summary report as
> > the feedback here, which is quite useful, such like pointing to the
> > bisected mail. This would take some time, and we will add to our TODO
> > as high priority.
>
> Yes, that would be much appreciated. You can also tag your reports with
> a unique hash which is then in an URL so that one can go and download the
> .config and what else is needed. For example...
>
> Thx.
>
> --
> Regards/Gruss,
> Boris.
>
> https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2020-09-17 14:10 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 [this message]
2020-10-12 9:16 ` Rong Chen
2020-10-12 14:37 ` Borislav Petkov
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=20200917133722.GA21986@intel.com \
--to=philip.li@intel.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@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