From: Marc Zyngier <maz@kernel.org>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Cc: kernel test robot <lkp@intel.com>,
Konrad Dybcio <konradybcio@kernel.org>,
Thomas Gleixner <tglx@kernel.org>, Radu Rendec <radu@rendec.net>,
Stephen Boyd <swboyd@chromium.org>,
Lina Iyer <ilina@codeaurora.org>,
llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
Abel Vesa <abel.vesa@oss.qualcomm.com>
Subject: Re: [PATCH] irqchip/qcom-pdc: Handle ESPIs in qcom,pdc-ranges
Date: Mon, 02 Nov 2026 15:33:54 +0000 [thread overview]
Message-ID: <86cxsn2qot.wl-maz@kernel.org> (raw)
In-Reply-To: <4a145c2f-24d3-48d2-8e84-3098604bcac4@oss.qualcomm.com>
On Mon, 02 Nov 2026 11:52:41 +0000,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com> wrote:
>
> On 10/27/26 2:08 AM, kernel test robot wrote:
> > Hi Konrad,
> >
> > kernel test robot noticed the following build errors:
> >
> > [auto build test ERROR on 2efb7a11f1aa4d2dc285fe2680cca22cb9f72f64]
> >
> > url: https://github.com/intel-lab-lkp/linux/commits/Konrad-Dybcio/irqchip-qcom-pdc-Handle-ESPIs-in-qcom-pdc-ranges/20261022-104402
> > base: 2efb7a11f1aa4d2dc285fe2680cca22cb9f72f64
> > patch link: https://lore.kernel.org/r/20261022-topic-pdc_map_espi-v1-1-7c481a42bac5%40oss.qualcomm.com
> > patch subject: [PATCH] irqchip/qcom-pdc: Handle ESPIs in qcom,pdc-ranges
> > config: hexagon-allmodconfig (https://download.01.org/0day-ci/archive/20261027/202610270827.7SxHabHO-lkp@intel.com/config)
> > compiler: clang version 24.0.0git (https://github.com/llvm/llvm-project 186e70f4e6a1521991d2340d3d49b23b1beff11f)
> > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261027/202610270827.7SxHabHO-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/202610270827.7SxHabHO-lkp@intel.com/
> >
> > All errors (new ones prefixed by >>):
> >
> > In file included from drivers/irqchip/qcom-pdc.c:12:
> >>> include/linux/irqchip/arm-gic-v3.h:605:10: fatal error: 'asm/arch_gicv3.h' file not found
> > 605 | #include <asm/arch_gicv3.h>
> > | ^~~~~~~~~~~~~~~~~~
>
> Marc, would you prefer that this is resolved by:
>
> * redefining the number in this driver
> * using the raw number, perhaps with a comment
> * making this only buildable and COMPILE_TEST-able on arm/64?
>
> I think 2 is reasonable
Works for me.
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2026-11-02 15:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20261022-topic-pdc_map_espi-v1-1-7c481a42bac5@oss.qualcomm.com>
2026-10-27 1:08 ` [PATCH] irqchip/qcom-pdc: Handle ESPIs in qcom,pdc-ranges kernel test robot
2026-11-02 11:52 ` Konrad Dybcio
2026-11-02 15:33 ` Marc Zyngier [this message]
2026-11-01 18:50 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=86cxsn2qot.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=abel.vesa@oss.qualcomm.com \
--cc=ilina@codeaurora.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=radu@rendec.net \
--cc=swboyd@chromium.org \
--cc=tglx@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.