From: Pavel Machek <pavel@ucw.cz>
To: Philip Li <philip.li@intel.com>
Cc: kernel test robot <lkp@intel.com>,
kernel list <linux-kernel@vger.kernel.org>,
Zheng Yongjun <zhengyongjun3@huawei.com>,
kbuild-all@lists.01.org, clang-built-linux@googlegroups.com,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [kbuild-all] Re: [linux-next:master 13538/13785] /tmp/metronomefb-846872.s:300: Error: unrecognized opcode `zext.b a2,a2'
Date: Sat, 19 Dec 2020 14:15:28 +0100 [thread overview]
Message-ID: <20201219131528.GA18240@duo.ucw.cz> (raw)
In-Reply-To: <20201219104006.GA14905@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1203 bytes --]
Hi!
> > > Crazy robot, stop spamming. This report is obviously bogus, yet, you
> > > sent me 5 copies.
> > Thanks Pavel for input, sorry for the false positive. It tries to
> > bisect error like below (the new error), but it may be related to
> > assember support. We will adjust the system to not report this out
> > wrongly. Kindly allow some time for us to resolving this.
> >
> > > > >> /tmp/metronomefb-846872.s:300: Error: unrecognized opcode `zext.b a2,a2'
> >
> > Thanks
> >
> > >
> > > Whoever is responsible for this, please sign emails with your real
> > > name!
> This is Philip who maintains the 0-day ci, and lkp@intel.com is the
> mailing list for the team here to be contacted.
Yes, so... 0-day bot normally does a really good job (and thanks for
it).
But getting emails from robot is slightly annoying, and it would be
nice to include name of person who is primary responsible from the bot
somewhere.
If you are primary person responsible for the robot, your name should
be somewhere in the email. Or perhaps the link in the trailer should
lead to explanation somewhere.
Best regards,
Pavel
--
http://www.livejournal.com/~pavelmachek
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2020-12-19 13:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-19 6:19 kernel test robot
2020-12-19 7:56 ` Pavel Machek
2020-12-19 10:28 ` [kbuild-all] " Philip Li
2020-12-19 10:40 ` Philip Li
2020-12-19 13:15 ` Pavel Machek [this message]
2020-12-19 14:25 ` Philip Li
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=20201219131528.GA18240@duo.ucw.cz \
--to=pavel@ucw.cz \
--cc=clang-built-linux@googlegroups.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=philip.li@intel.com \
--cc=zhengyongjun3@huawei.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