From: Philip Li <philip.li@intel.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: kernel test robot <lkp@intel.com>,
Zheng Yongjun <zhengyongjun3@huawei.com>,
kbuild-all@lists.01.org, clang-built-linux@googlegroups.com,
Linux Memory Management List <linux-mm@kvack.org>,
Alexander Dahl <ada@thorsis.com>
Subject: Re: [kbuild-all] Re: [linux-next:master 13540/13785] /tmp/do_mounts-997907.s:184: Error: unrecognized opcode `zext.b a1,a0'
Date: Sat, 19 Dec 2020 18:29:03 +0800 [thread overview]
Message-ID: <20201219102903.GB14085@intel.com> (raw)
In-Reply-To: <20201219004521.GA18304@amd>
On Sat, Dec 19, 2020 at 01:45:21AM +0100, Pavel Machek wrote:
> Robot went crazy.
sorry, kindly ignore this false positive, we will resolve this
problem in earliest time.
>
> Nothing to be seen here AFAICT.
>
> > commit: 232aa16455db7fc1edb61878853d620067a30fe5 [13540/13785] leds:
> leds-ariel: convert comma to semicolon
>
> This commit is not relevant for risc-v (and does not really change
> anything), and does not even touch init/do_mounts.c...
>
> > In file included from init/do_mounts.c:7:
> > In file included from include/linux/suspend.h:5:
> > In file included from include/linux/swap.h:9:
>
> Best regards,
>
> Pavel
> --
> http://www.livejournal.com/~pavelmachek
> _______________________________________________
> kbuild-all mailing list -- kbuild-all@lists.01.org
> To unsubscribe send an email to kbuild-all-leave@lists.01.org
prev parent reply other threads:[~2020-12-19 10:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-19 0:28 [linux-next:master 13540/13785] /tmp/do_mounts-997907.s:184: Error: unrecognized opcode `zext.b a1,a0' kernel test robot
2020-12-19 0:45 ` Pavel Machek
2020-12-19 10:29 ` Philip Li [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=20201219102903.GB14085@intel.com \
--to=philip.li@intel.com \
--cc=ada@thorsis.com \
--cc=clang-built-linux@googlegroups.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=pavel@ucw.cz \
--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;
as well as URLs for NNTP newsgroup(s).