Re: [PATCH v4] watchdog: alim1535: Rewriting of alim1535 to use watchdog subsystem

2019-08-01 Thread Mark Balantzyan
Please see: https://lkml.org/lkml/2019/8/2/6 Thank you.

Re: [PATCH v4] watchdog: alim1535: Rewriting of alim1535 to use watchdog subsystem

2019-08-01 Thread Mark Balantzyan
There was some sort of filesystem error that cause the wrong file to be saved. Hence, yes, possibly there was no difference betwee the v2 and the 'v4' (which should have been the 'v3'). Since the last one, though unchanged from v2, was a changelog-less 'v3', THIS is an actual 'v4'. Thank you,

Re: [PATCH v4] watchdog: alim1535: Rewriting of alim1535 to use watchdog subsystem

2019-08-01 Thread Mark Balantzyan
Take a second look. It is different. And I had to amend the title hence the second send to include the subsystem, as you so duly tend to remind me. It just so happened that I mistyped and skipped a version by...1. Mark On Thu, 1 Aug 2019, Guenter Roeck wrote: On 8/1/19 8:26 PM, Mark Balantzy

Re: [PATCH v4] watchdog: alim1535: Rewriting of alim1535 to use watchdog subsystem

2019-08-01 Thread Guenter Roeck
On 8/1/19 8:26 PM, Mark Balantzyan wrote: This patch rewrites the alim1535_wdt driver to use the watchdog subsystem. By virtue of this, it also fixes a (theoretical) race condition between the formerly arranged ali_timeout_bits and ali_settimer() interoperation. Signed-off-by: Mark Balantzyan

[PATCH v4] watchdog: alim1535: Rewriting of alim1535 to use watchdog subsystem

2019-08-01 Thread Mark Balantzyan
This patch rewrites the alim1535_wdt driver to use the watchdog subsystem. By virtue of this, it also fixes a (theoretical) race condition between the formerly arranged ali_timeout_bits and ali_settimer() interoperation. Signed-off-by: Mark Balantzyan --- drivers/watchdog/Kconfig| 1