From: Pavel Machek <pavel@ucw.cz>
To: kbuild-all@lists.01.org
Subject: Re: [linux-next:master 13540/13785] /tmp/do_mounts-997907.s:184: Error: unrecognized opcode `zext.b a1, a0'
Date: Sat, 19 Dec 2020 01:45:21 +0100 [thread overview]
Message-ID: <20201219004521.GA18304@amd> (raw)
In-Reply-To: <202012190800.zhlTY0rf-lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 541 bytes --]
Robot went crazy.
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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Pavel Machek <pavel@ucw.cz>
To: kernel test robot <lkp@intel.com>
Cc: 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: [linux-next:master 13540/13785] /tmp/do_mounts-997907.s:184: Error: unrecognized opcode `zext.b a1,a0'
Date: Sat, 19 Dec 2020 01:45:21 +0100 [thread overview]
Message-ID: <20201219004521.GA18304@amd> (raw)
In-Reply-To: <202012190800.zhlTY0rf-lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 541 bytes --]
Robot went crazy.
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
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2020-12-19 0:45 UTC|newest]
Thread overview: 6+ 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: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 [this message]
2020-12-19 0:45 ` Pavel Machek
2020-12-19 10:29 ` [linux-next:master 13540/13785] /tmp/do_mounts-997907.s:184: Error: unrecognized opcode `zext.b a1, a0' Philip Li
2020-12-19 10:29 ` [kbuild-all] Re: [linux-next:master 13540/13785] /tmp/do_mounts-997907.s:184: Error: unrecognized opcode `zext.b a1,a0' 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=20201219004521.GA18304@amd \
--to=pavel@ucw.cz \
--cc=kbuild-all@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.