[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b7da8789-6c55-cf41-b95a-e87f9341c438@roeck-us.net>
Date: Mon, 6 Feb 2023 05:55:40 -0800
From: Guenter Roeck <linux@...ck-us.net>
To: Heiko Carstens <hca@...ux.ibm.com>,
Wim Van Sebroeck <wim@...ux-watchdog.org>
Cc: linux-watchdog@...r.kernel.org, linux-kernel@...r.kernel.org,
Alexander Egorenkov <egorenar@...ux.ibm.com>
Subject: Re: [PATCH 0/5] diag288 watchdog fixes and improvements
On 2/6/23 01:59, Heiko Carstens wrote:
> On Fri, Feb 03, 2023 at 08:39:53AM +0100, Alexander Egorenkov wrote:
>> Minor code refactoring to improve readability of the driver,
>> reduce code duplication and remove dead code.
>>
>> Alexander Egorenkov (5):
>> watchdog: diag288_wdt: get rid of register asm
>> watchdog: diag288_wdt: remove power management
>> watchdog: diag288_wdt: unify command buffer handling for diag288 zvm
>> watchdog: diag288_wdt: de-duplicate diag_stat_inc() calls
>> watchdog: diag288_wdt: unify lpar and zvm diag288 helpers
>>
>> drivers/watchdog/diag288_wdt.c | 162 ++++++++-------------------------
>> 1 file changed, 37 insertions(+), 125 deletions(-)
>
> Guenter, Wim, how should this go upstream?
>
> I can easily pick this up via the s390 tree for the next merge window.
> Please let me know.
>
I have it currently in my watchdog-next tree, but that is not in linux-next.
Fine with me to go through the s390 tree.
Guenter
Powered by blists - more mailing lists