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>,
llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] clk: microchip: core: allow driver to be compiled with COMPILE_TEST
Date: Mon, 1 Dec 2025 13:01:25 -0500 [thread overview]
Message-ID: <aS3X9VXVlKNQyDoz@redhat.com> (raw)
In-Reply-To: <202511270924.0uDTpEE9-lkp@intel.com>
On Thu, Nov 27, 2025 at 10:11:12AM +0800, kernel test robot wrote:
> Hi Brian,
>
> kernel test robot noticed the following build errors:
>
> [auto build test ERROR on 92fd6e84175befa1775e5c0ab682938eca27c0b2]
>
> url: https://github.com/intel-lab-lkp/linux/commits/Brian-Masney/clk-microchip-core-remove-duplicate-determine_rate-on-pic32_sclk_ops/20251126-035403
> base: 92fd6e84175befa1775e5c0ab682938eca27c0b2
> patch link: https://lore.kernel.org/r/20251125-clk-microchip-fixes-v1-2-6c1f5573d1b9%40redhat.com
> patch subject: [PATCH 2/2] clk: microchip: core: allow driver to be compiled with COMPILE_TEST
> config: loongarch-randconfig-001-20251127 (https://download.01.org/0day-ci/archive/20251127/202511270924.0uDTpEE9-lkp@intel.com/config)
> compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project 9e9fe08b16ea2c4d9867fb4974edf2a3776d6ece)
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251127/202511270924.0uDTpEE9-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/202511270924.0uDTpEE9-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
> >> drivers/clk/microchip/clk-core.c:12:10: fatal error: 'asm/traps.h' file not found
> 12 | #include <asm/traps.h>
> | ^~~~~~~~~~~~~
> 1 error generated.
>
> Kconfig warnings: (for reference only)
> WARNING: unmet direct dependencies detected for TSM
> Depends on [n]: VIRT_DRIVERS [=n]
> Selected by [y]:
> - PCI_TSM [=y] && PCI [=y]
>
>
> vim +12 drivers/clk/microchip/clk-core.c
>
> ce6e1188465998 Purna Chandra Mandal 2016-05-13 @12 #include <asm/traps.h>
> ce6e1188465998 Purna Chandra Mandal 2016-05-13 13
I only build tested this on arm64. I'll post a v2.
Thanks,
Brian
next prev parent reply other threads:[~2025-12-01 18:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 19:39 [PATCH 0/2] clk: microchip: core: fix issue with round_rate conversion and allow compile test Brian Masney
2025-11-25 19:39 ` [PATCH 1/2] clk: microchip: core: remove duplicate determine_rate on pic32_sclk_ops Brian Masney
2025-11-25 19:39 ` [PATCH 2/2] clk: microchip: core: allow driver to be compiled with COMPILE_TEST Brian Masney
2025-11-27 2:11 ` kernel test robot
2025-12-01 18:01 ` Brian Masney [this message]
2025-12-01 18:09 ` Conor Dooley
2025-12-01 21:09 ` Brian Masney
2025-12-01 21:37 ` Conor Dooley
2025-11-27 5:28 ` kernel test robot
2025-11-27 10:49 ` kernel test robot
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=aS3X9VXVlKNQyDoz@redhat.com \
--to=bmasney@redhat.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--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 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.