Re: [PATCH 4/7] watchdog/hardlockup: Enable HAVE_NMI_WATCHDOG only on sparc64

2023-06-08 Thread Petr Mladek
On Wed 2023-06-07 16:36:35, Doug Anderson wrote: > Hi, > > On Wed, Jun 7, 2023 at 8:25 AM Petr Mladek wrote: > > > > diff --git a/arch/Kconfig b/arch/Kconfig > > index 13c6e596cf9e..57f15babe188 100644 > > --- a/arch/Kconfig > > +++ b/arch/Kconfig > > @@ -404,10 +404,9 @@ config

Re: [PATCH 4/7] watchdog/hardlockup: Enable HAVE_NMI_WATCHDOG only on sparc64

2023-06-07 Thread Doug Anderson
Hi, On Wed, Jun 7, 2023 at 8:25 AM Petr Mladek wrote: > > diff --git a/arch/Kconfig b/arch/Kconfig > index 13c6e596cf9e..57f15babe188 100644 > --- a/arch/Kconfig > +++ b/arch/Kconfig > @@ -404,10 +404,9 @@ config HAVE_NMI_WATCHDOG > depends on HAVE_NMI > bool > help > -

[PATCH 4/7] watchdog/hardlockup: Enable HAVE_NMI_WATCHDOG only on sparc64

2023-06-07 Thread Petr Mladek
HAVE_NMI_WATCHDOG is always enabled when SPARC64 is enabled. The sparc64 implementation is special. It does not support the generic hardlockup related Kconfig values, command line parameters, and sysctl interface. Instead it is enabled/disabled by the top-level watchdog interface that is common