From: Brian Masney <bmasney@redhat.com>
To: Nathan Chancellor <nathan@kernel.org>
Cc: kernel test robot <lkp@intel.com>,
llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH 13/13] clk: microchip: core: allow driver to be compiled with COMPILE_TEST
Date: Thu, 22 Jan 2026 07:31:14 -0500 [thread overview]
Message-ID: <aXIYklgDnskI1HXe@redhat.com> (raw)
In-Reply-To: <20260121231321.GB2625738@ax162>
On Wed, Jan 21, 2026 at 04:13:21PM -0700, Nathan Chancellor wrote:
> On Tue, Jan 20, 2026 at 12:46:32PM -0500, Brian Masney wrote:
> > None of the errors in this report appear to be due to the changes that
> > I made that allow drivers/clk/microchip/clk-core.c to be compiled on all
> > architectures instead of just MIPS.
>
> Well, it is just the fact that this code is now compiled on all
> architectures via CONFIG_COMPILE_TEST, right? asm/traps.h is an
> architecture specific header, which might not work when used outside of
> arch/${SRCARCH}. In this case, x86's traps.h is used for arch/um but
> arch/um has never used this header before because all generic uses are
> gated on specific architectures like in this case.
>
> Is this header needed when compile testing or could it be gated on
> CONFIG_MIPS?
I changed it so that it's gated on CONFIG_MIPS and it's working on
several arches.
Brian
prev parent reply other threads:[~2026-01-22 12:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260109-mips-pic32-header-move-v1-13-99859c55783d@redhat.com>
2026-01-16 13:20 ` [PATCH 13/13] clk: microchip: core: allow driver to be compiled with COMPILE_TEST kernel test robot
2026-01-20 17:46 ` Brian Masney
2026-01-21 23:13 ` Nathan Chancellor
2026-01-22 12:31 ` Brian Masney [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=aXIYklgDnskI1HXe@redhat.com \
--to=bmasney@redhat.com \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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