Re: linux-next: Tree for Aug 28 (loongarch: kgdb)

[Randy Dunlap <rdunlap@infradead.org>]

On 8/27/23 22:02, Stephen Rothwell wrote:
> Hi all,
> 
> Please do *not* include material destined for v6.7 in your linux-next
> included branches until *after* v6.6-rc1 has been released.  Also,
> do *not* rebase you linu-next included branches onto v6.5.
> 
> Changes since 20230825:
> 

There are many build errors when CONFIG_PERF_EVENTS => HAVE_HW_BREAKPOINT
are not set.
This is a reduced list of the build errors:

../arch/loongarch/kernel/kgdb.c: In function 'hw_break_reserve_slot':
../arch/loongarch/kernel/kgdb.c:515:21: error: implicit declaration of function 'dbg_reserve_bp_slot'; did you mean 'reserve_bp_slot'? [-Werror=implicit-function-declaration]
  515 |                 if (dbg_reserve_bp_slot(*pevent))
      |                     ^~~~~~~~~~~~~~~~~~~
      |                     reserve_bp_slot
../arch/loongarch/kernel/kgdb.c:527:17: error: implicit declaration of function 'dbg_release_bp_slot'; did you mean 'release_bp_slot'? [-Werror=implicit-function-declaration]
  527 |                 dbg_release_bp_slot(*pevent);
      |                 ^~~~~~~~~~~~~~~~~~~
      |                 release_bp_slot
../arch/loongarch/kernel/kgdb.c: In function 'kgdb_disable_hw_break':
../arch/loongarch/kernel/kgdb.c:640:23: error: 'struct perf_event' has no member named 'attr'
  640 |                 if (bp->attr.disabled == 1)
      |                       ^~
../arch/loongarch/kernel/kgdb.c: In function 'kgdb_arch_late':
../arch/loongarch/kernel/kgdb.c:732:9: error: implicit declaration of function 'hw_breakpoint_init'; did you mean 'hw_breakpoint_slots'? [-Werror=implicit-function-declaration]
  732 |         hw_breakpoint_init(&attr);
      |         ^~~~~~~~~~~~~~~~~~
      |         hw_breakpoint_slots
../arch/loongarch/kernel/kgdb.c:752:38: error: 'struct perf_event' has no member named 'destroy'
  752 |                         if (pevent[0]->destroy) {
      |                                      ^~
cc1: some warnings being treated as errors


-- 
~Randy