From: Marc Zyngier <maz@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: Shanker Donthineni <sdonthineni@nvidia.com>,
Paul Gazzillo <paul@pgazz.com>,
Necip Fazil Yildiran <fazilyildiran@gmail.com>,
oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Vikram Sethi <vsethi@nvidia.com>
Subject: Re: kismet: WARNING: unmet direct dependencies detected for HAVE_ARM_SMCCC_DISCOVERY when selected by ARM_GIC_V3
Date: Thu, 27 Aug 2026 13:14:16 +0100 [thread overview]
Message-ID: <86qzjj4v6v.wl-maz@kernel.org> (raw)
In-Reply-To: <202608262054.WWa7JMca-lkp@intel.com>
On Wed, 26 Aug 2026 19:43:49 +0100,
kernel test robot <lkp@intel.com> wrote:
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: 45c13f3f9e3bb15fd89ff2864c6f627a3b4b4229
> commit: 35727af2b15d98a2dd2811d631d3a3886111312e irqchip/gicv3: Workaround for NVIDIA erratum T241-FABRIC-4
> date: 3 years, 5 months ago
> config: arm-kismet-CONFIG_HAVE_ARM_SMCCC_DISCOVERY-CONFIG_ARM_GIC_V3-0-0 (https://download.01.org/0day-ci/archive/20260826/202608262054.WWa7JMca-lkp@intel.com/config)
> reproduce: (https://download.01.org/0day-ci/archive/20260826/202608262054.WWa7JMca-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
> | Fixes: 35727af2b15d ("irqchip/gicv3: Workaround for NVIDIA erratum T241-FABRIC-4")
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202608262054.WWa7JMca-lkp@intel.com/
>
> kismet warnings: (new ones prefixed by >>)
> >> kismet: WARNING: unmet direct dependencies detected for HAVE_ARM_SMCCC_DISCOVERY when selected by ARM_GIC_V3
> WARNING: unmet direct dependencies detected for HAVE_ARM_SMCCC_DISCOVERY
> Depends on [n]: ARM_PSCI_FW [=n]
> Selected by [y]:
> - ARM_GIC_V3 [=y]
>
See 20260823180832.1246363-1-julianbraha@gmail.com.
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2026-08-27 12:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-26 18:43 kernel test robot
2026-08-27 12:14 ` Marc Zyngier [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-01-11 21:31 kernel test robot
2025-12-09 17:44 kernel test robot
2025-05-20 10:45 kernel test robot
2025-04-12 7:28 kernel test robot
2023-11-06 8:23 kernel test robot
2023-11-04 10:10 kernel test robot
2023-11-03 9:22 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=86qzjj4v6v.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=fazilyildiran@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=paul@pgazz.com \
--cc=sdonthineni@nvidia.com \
--cc=vsethi@nvidia.com \
/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
all inboxes | Powered by JetHome®