From: Heiko Carstens <hca@linux.ibm.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Wim Van Sebroeck <wim@linux-watchdog.org>,
linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org,
Alexander Egorenkov <egorenar@linux.ibm.com>
Subject: Re: [PATCH 0/5] diag288 watchdog fixes and improvements
Date: Mon, 6 Feb 2023 15:33:23 +0100 [thread overview]
Message-ID: <Y+EPs2EQEevzhpvB@osiris> (raw)
In-Reply-To: <b7da8789-6c55-cf41-b95a-e87f9341c438@roeck-us.net>
On Mon, Feb 06, 2023 at 05:55:40AM -0800, Guenter Roeck wrote:
> 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.
Applied to s390 tree - should be in next linux-next release.
Thank you!
prev parent reply other threads:[~2023-02-06 14:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 7:39 [PATCH 0/5] diag288 watchdog fixes and improvements Alexander Egorenkov
2023-02-03 7:39 ` [PATCH 1/5] watchdog: diag288_wdt: get rid of register asm Alexander Egorenkov
2023-02-03 18:17 ` Guenter Roeck
2023-02-03 7:39 ` [PATCH 2/5] watchdog: diag288_wdt: remove power management Alexander Egorenkov
2023-02-03 18:23 ` Guenter Roeck
2023-02-03 7:39 ` [PATCH 3/5] watchdog: diag288_wdt: unify command buffer handling for diag288 zvm Alexander Egorenkov
2023-02-03 18:34 ` Guenter Roeck
2023-02-03 7:39 ` [PATCH 4/5] watchdog: diag288_wdt: de-duplicate diag_stat_inc() calls Alexander Egorenkov
2023-02-03 18:36 ` Guenter Roeck
2023-02-03 7:39 ` [PATCH 5/5] watchdog: diag288_wdt: unify lpar and zvm diag288 helpers Alexander Egorenkov
2023-02-03 18:37 ` Guenter Roeck
2023-02-06 9:59 ` [PATCH 0/5] diag288 watchdog fixes and improvements Heiko Carstens
2023-02-06 13:55 ` Guenter Roeck
2023-02-06 14:33 ` Heiko Carstens [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y+EPs2EQEevzhpvB@osiris \
--to=hca@linux.ibm.com \
--cc=egorenar@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=wim@linux-watchdog.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.