From: Nathan Chancellor <nathan@kernel.org>
To: Brian Masney <bmasney@redhat.com>
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: Wed, 21 Jan 2026 16:13:21 -0700 [thread overview]
Message-ID: <20260121231321.GB2625738@ax162> (raw)
In-Reply-To: <aW-_eIjcRp7VM0bt@redhat.com>
On Tue, Jan 20, 2026 at 12:46:32PM -0500, Brian Masney wrote:
> On Fri, Jan 16, 2026 at 09:20:36PM +0800, kernel test robot wrote:
> > Hi Brian,
> >
> > kernel test robot noticed the following build errors:
> >
> > [auto build test ERROR on f417b7ffcbef7d76b0d8860518f50dae0e7e5eda]
> >
> > url: https://github.com/intel-lab-lkp/linux/commits/Brian-Masney/MIPS-copy-pic32-h-header-file-from-asm-mach-pic32-to-include-platform-data/20260110-005057
> > base: f417b7ffcbef7d76b0d8860518f50dae0e7e5eda
> > patch link: https://lore.kernel.org/r/20260109-mips-pic32-header-move-v1-13-99859c55783d%40redhat.com
> > patch subject: [PATCH 13/13] clk: microchip: core: allow driver to be compiled with COMPILE_TEST
> > config: um-allmodconfig (https://download.01.org/0day-ci/archive/20260116/202601162110.K1eWGORM-lkp@intel.com/config)
> > compiler: clang version 19.1.7 (https://github.com/llvm/llvm-project cd708029e0b2869e80abe31ddb175f7c35361f90)
> > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260116/202601162110.K1eWGORM-lkp@intel.com/reproduce)
> >
> > If you fix the issue in a separate patch/commit (i.e. not just a new version of
> > the same patch/commit), kindly add following tags
> > | Reported-by: kernel test robot <lkp@intel.com>
> > | Closes: https://lore.kernel.org/oe-kbuild-all/202601162110.K1eWGORM-lkp@intel.com/
>
> 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?
Cheers,
Nathan
next prev parent reply other threads:[~2026-01-21 23:13 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 [this message]
2026-01-22 12:31 ` 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=20260121231321.GB2625738@ax162 \
--to=nathan@kernel.org \
--cc=bmasney@redhat.com \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--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