From: kernel test robot <lkp@intel.com>
To: Himanshu Chauhan <hchauhan@ventanamicro.com>
Cc: Paul Gazzillo <paul@pgazz.com>,
Necip Fazil Yildiran <fazilyildiran@gmail.com>,
oe-kbuild-all@lists.linux.dev, Anup Patel <anup@brainfault.org>,
Jesse Taube <jesse@rivosinc.com>
Subject: [avpatel:riscv_acpi_apei_v1 35/55] kismet: WARNING: unmet direct dependencies detected for HAVE_MIXED_BREAKPOINTS_REGS when selected by RISCV
Date: Tue, 12 Aug 2025 05:23:55 +0800 [thread overview]
Message-ID: <202508120533.rLMGb1Fl-lkp@intel.com> (raw)
tree: https://github.com/avpatel/linux.git riscv_acpi_apei_v1
head: eaca137f211dcb260f7eb52d983ddad7f27277f3
commit: df85c5a81bf62ede57ad6bdfa14482907dee11cf [35/55] riscv: Introduce support for hardware break/watchpoints
config: riscv-kismet-CONFIG_HAVE_MIXED_BREAKPOINTS_REGS-CONFIG_RISCV-0-0 (https://download.01.org/0day-ci/archive/20250812/202508120533.rLMGb1Fl-lkp@intel.com/config)
reproduce: (https://download.01.org/0day-ci/archive/20250812/202508120533.rLMGb1Fl-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/202508120533.rLMGb1Fl-lkp@intel.com/
kismet warnings: (new ones prefixed by >>)
>> kismet: WARNING: unmet direct dependencies detected for HAVE_MIXED_BREAKPOINTS_REGS when selected by RISCV
WARNING: unmet direct dependencies detected for HAVE_MIXED_BREAKPOINTS_REGS
Depends on [n]: HAVE_HW_BREAKPOINT [=n]
Selected by [y]:
- RISCV [=y]
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-08-11 21:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202508120533.rLMGb1Fl-lkp@intel.com \
--to=lkp@intel.com \
--cc=anup@brainfault.org \
--cc=fazilyildiran@gmail.com \
--cc=hchauhan@ventanamicro.com \
--cc=jesse@rivosinc.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=paul@pgazz.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 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.