Re: [PATCH v4 0/5] Improve watchdog config for arch watchdogs

2017-06-16 Thread Babu Moger
Tested on sparc: Tested-by: Babu Moger Reviewed patch #1, #2, #3 Reviewed-by: Babu Moger On 6/16/2017 9:50 AM, Don Zickus wrote: (adding Andrew) On Fri, Jun 16, 2017 at 04:57:10PM +1000, Nicholas Piggin wrote: This is the latest series to

Re: [PATCH v4 0/5] Improve watchdog config for arch watchdogs

2017-06-16 Thread Babu Moger
Tested on sparc: Tested-by: Babu Moger Reviewed patch #1, #2, #3 Reviewed-by: Babu Moger On 6/16/2017 9:50 AM, Don Zickus wrote: (adding Andrew) On Fri, Jun 16, 2017 at 04:57:10PM +1000, Nicholas Piggin wrote: This is the latest series to make the hardlockup watchdog more easily

Re: [PATCH v4 0/5] Improve watchdog config for arch watchdogs

2017-06-16 Thread Don Zickus
(adding Andrew) On Fri, Jun 16, 2017 at 04:57:10PM +1000, Nicholas Piggin wrote: > This is the latest series to make the hardlockup watchdog more > easily replaceable by arch code. The last patch provides some > justification for why we want to do this (existing sparc watchdog > is another that

Re: [PATCH v4 0/5] Improve watchdog config for arch watchdogs

2017-06-16 Thread Don Zickus
(adding Andrew) On Fri, Jun 16, 2017 at 04:57:10PM +1000, Nicholas Piggin wrote: > This is the latest series to make the hardlockup watchdog more > easily replaceable by arch code. The last patch provides some > justification for why we want to do this (existing sparc watchdog > is another that

[PATCH v4 0/5] Improve watchdog config for arch watchdogs

2017-06-16 Thread Nicholas Piggin
This is the latest series to make the hardlockup watchdog more easily replaceable by arch code. The last patch provides some justification for why we want to do this (existing sparc watchdog is another that could benefit). Since last time, we tidied up the Kconfig approach so it was not so

[PATCH v4 0/5] Improve watchdog config for arch watchdogs

2017-06-16 Thread Nicholas Piggin
This is the latest series to make the hardlockup watchdog more easily replaceable by arch code. The last patch provides some justification for why we want to do this (existing sparc watchdog is another that could benefit). Since last time, we tidied up the Kconfig approach so it was not so