All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Guenter Roeck <linux@roeck-us.net>,
	Scott Cheloha <cheloha@linux.ibm.com>
Cc: linux-watchdog@vger.kernel.org, tzungbi@kernel.org,
	brking@linux.ibm.com, nathanl@linux.ibm.com, aik@ozlabs.ru,
	npiggin@gmail.com, vaishnavi@linux.ibm.com, wvoigt@us.ibm.com,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v3 4/4] watchdog/pseries-wdt: initial support for H_WATCHDOG-based watchdog timers
Date: Tue, 26 Jul 2022 17:14:03 +1000	[thread overview]
Message-ID: <87bktcbb2c.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <20220725213026.GA1319556@roeck-us.net>

Guenter Roeck <linux@roeck-us.net> writes:
> On Mon, Jul 25, 2022 at 11:11:41AM -0500, Scott Cheloha wrote:
>> On Wed, Jul 13, 2022 at 01:50:14PM -0700, Guenter Roeck wrote:
>> > On 7/13/22 13:23, Scott Cheloha wrote:
>> > > PAPR v2.12 defines a new hypercall, H_WATCHDOG.  The hypercall permits
>> > > guest control of one or more virtual watchdog timers.  The timers have
>> > > millisecond granularity.  The guest is terminated when a timer
>> > > expires.
>> > > 
>> > > This patch adds a watchdog driver for these timers, "pseries-wdt".
>> > > 
>> > > pseries_wdt_probe() currently assumes the existence of only one
>> > > platform device and always assigns it watchdogNumber 1.  If we ever
>> > > expose more than one timer to userspace we will need to devise a way
>> > > to assign a distinct watchdogNumber to each platform device at device
>> > > registration time.
>> > > 
>> > > Signed-off-by: Scott Cheloha <cheloha@linux.ibm.com>
>> > 
>> > Acked-by: Guenter Roeck <linux@roeck-us.net>
>> 
>> Guenter, Michael,
>> 
>> Which tree is taking this series?

powerpc.

It's been in next-test/next for about a week.

It's in linux-next today.

> The series includes non-watchdog changes, so my expectation was that some
> other tree would take it.

Yep, thanks for the ack.

cheers

WARNING: multiple messages have this Message-ID (diff)
From: Michael Ellerman <mpe@ellerman.id.au>
To: Guenter Roeck <linux@roeck-us.net>,
	Scott Cheloha <cheloha@linux.ibm.com>
Cc: nathanl@linux.ibm.com, wvoigt@us.ibm.com,
	linux-watchdog@vger.kernel.org, aik@ozlabs.ru,
	vaishnavi@linux.ibm.com, npiggin@gmail.com, tzungbi@kernel.org,
	brking@linux.ibm.com, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v3 4/4] watchdog/pseries-wdt: initial support for H_WATCHDOG-based watchdog timers
Date: Tue, 26 Jul 2022 17:14:03 +1000	[thread overview]
Message-ID: <87bktcbb2c.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <20220725213026.GA1319556@roeck-us.net>

Guenter Roeck <linux@roeck-us.net> writes:
> On Mon, Jul 25, 2022 at 11:11:41AM -0500, Scott Cheloha wrote:
>> On Wed, Jul 13, 2022 at 01:50:14PM -0700, Guenter Roeck wrote:
>> > On 7/13/22 13:23, Scott Cheloha wrote:
>> > > PAPR v2.12 defines a new hypercall, H_WATCHDOG.  The hypercall permits
>> > > guest control of one or more virtual watchdog timers.  The timers have
>> > > millisecond granularity.  The guest is terminated when a timer
>> > > expires.
>> > > 
>> > > This patch adds a watchdog driver for these timers, "pseries-wdt".
>> > > 
>> > > pseries_wdt_probe() currently assumes the existence of only one
>> > > platform device and always assigns it watchdogNumber 1.  If we ever
>> > > expose more than one timer to userspace we will need to devise a way
>> > > to assign a distinct watchdogNumber to each platform device at device
>> > > registration time.
>> > > 
>> > > Signed-off-by: Scott Cheloha <cheloha@linux.ibm.com>
>> > 
>> > Acked-by: Guenter Roeck <linux@roeck-us.net>
>> 
>> Guenter, Michael,
>> 
>> Which tree is taking this series?

powerpc.

It's been in next-test/next for about a week.

It's in linux-next today.

> The series includes non-watchdog changes, so my expectation was that some
> other tree would take it.

Yep, thanks for the ack.

cheers

  reply	other threads:[~2022-07-26  7:14 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-13 20:23 [PATCH v3 0/4] pseries-wdt: initial support for H_WATCHDOG-based watchdog timers Scott Cheloha
2022-07-13 20:23 ` Scott Cheloha
2022-07-13 20:23 ` [PATCH v3 1/4] powerpc/pseries: hvcall.h: add H_WATCHDOG opcode, H_NOOP return code Scott Cheloha
2022-07-13 20:23   ` Scott Cheloha
2022-07-13 20:23 ` [PATCH v3 2/4] powerpc/pseries: add FW_FEATURE_WATCHDOG flag Scott Cheloha
2022-07-13 20:23   ` Scott Cheloha
2022-07-13 20:23 ` [PATCH v3 3/4] powerpc/pseries: register pseries-wdt device with platform bus Scott Cheloha
2022-07-13 20:23   ` Scott Cheloha
2022-07-13 20:23 ` [PATCH v3 4/4] watchdog/pseries-wdt: initial support for H_WATCHDOG-based watchdog timers Scott Cheloha
2022-07-13 20:23   ` Scott Cheloha
2022-07-13 20:50   ` Guenter Roeck
2022-07-13 20:50     ` Guenter Roeck
2022-07-25 16:11     ` Scott Cheloha
2022-07-25 16:11       ` Scott Cheloha
2022-07-25 21:30       ` Guenter Roeck
2022-07-25 21:30         ` Guenter Roeck
2022-07-26  7:14         ` Michael Ellerman [this message]
2022-07-26  7:14           ` Michael Ellerman
2022-07-29 13:01 ` [PATCH v3 0/4] pseries-wdt: " Michael Ellerman
2022-07-29 13:01   ` Michael Ellerman

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=87bktcbb2c.fsf@mpe.ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=aik@ozlabs.ru \
    --cc=brking@linux.ibm.com \
    --cc=cheloha@linux.ibm.com \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=nathanl@linux.ibm.com \
    --cc=npiggin@gmail.com \
    --cc=tzungbi@kernel.org \
    --cc=vaishnavi@linux.ibm.com \
    --cc=wvoigt@us.ibm.com \
    /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.