From: Brian Masney <bmasney@redhat.com>
To: kernel test robot <lkp@intel.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Maxime Ripard <mripard@kernel.org>,
Claudiu Beznea <claudiu.beznea@tuxon.dev>,
Conor Dooley <conor@kernel.org>,
oe-kbuild-all@lists.linux.dev, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/3] clk: microchip: core: allow driver to be compiled with COMPILE_TEST
Date: Fri, 5 Dec 2025 06:33:47 -0500 [thread overview]
Message-ID: <aTLDG_LEGQwgJUwg@redhat.com> (raw)
In-Reply-To: <202512051151.N3iZUKEG-lkp@intel.com>
On Fri, Dec 05, 2025 at 11:51:12AM +0800, kernel test robot wrote:
> drivers/clk/microchip/clk-core.c: Assembler messages:
> >> drivers/clk/microchip/clk-core.c:721: Error: unrecognized instruction `nop'
> >> drivers/clk/microchip/clk-core.c:721: Error: unrecognized instruction `nop'
> >> drivers/clk/microchip/clk-core.c:721: Error: unrecognized instruction `nop'
> >> drivers/clk/microchip/clk-core.c:721: Error: unrecognized instruction `nop'
> >> drivers/clk/microchip/clk-core.c:721: Error: unrecognized instruction `nop'
> drivers/clk/microchip/clk-core.c:722: Error: unrecognized instruction `nop'
> drivers/clk/microchip/clk-core.c:722: Error: unrecognized instruction `nop'
> drivers/clk/microchip/clk-core.c:722: Error: unrecognized instruction `nop'
> drivers/clk/microchip/clk-core.c:722: Error: unrecognized instruction `nop'
> drivers/clk/microchip/clk-core.c:722: Error: unrecognized instruction `nop'
> drivers/clk/microchip/clk-core.c:862: Error: unrecognized instruction `nop'
> drivers/clk/microchip/clk-core.c:862: Error: unrecognized instruction `nop'
> drivers/clk/microchip/clk-core.c:862: Error: unrecognized instruction `nop'
> drivers/clk/microchip/clk-core.c:862: Error: unrecognized instruction `nop'
> drivers/clk/microchip/clk-core.c:862: Error: unrecognized instruction `nop'
That's related to these calls: __asm__ __volatile__("nop");
In the case of compile test, I'll just make this a noop. I'll post a new
version.
Brian
next prev parent reply other threads:[~2025-12-05 11:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-01 22:06 [PATCH v2 0/3] clk: microchip: core: fix issue with round_rate conversion and allow compile test Brian Masney
2025-12-01 22:06 ` [PATCH v2 1/3] clk: microchip: core: remove duplicate determine_rate on pic32_sclk_ops Brian Masney
2025-12-01 22:06 ` [PATCH v2 2/3] clk: microchip: core: remove unused include asm/traps.h Brian Masney
2025-12-01 22:06 ` [PATCH v2 3/3] clk: microchip: core: allow driver to be compiled with COMPILE_TEST Brian Masney
2025-12-05 3:51 ` kernel test robot
2025-12-05 11:33 ` Brian Masney [this message]
2025-12-05 7:21 ` Dan Carpenter
2025-12-05 11:35 ` Brian Masney
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=aTLDG_LEGQwgJUwg@redhat.com \
--to=bmasney@redhat.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=conor@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mripard@kernel.org \
--cc=mturquette@baylibre.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sboyd@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;
as well as URLs for NNTP newsgroup(s).