All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Nathan Lynch <nathanl@linux.ibm.com>,
	Scott Cheloha <cheloha@linux.ibm.com>,
	linux-watchdog@vger.kernel.org
Cc: wvoigt@us.ibm.com, aik@ozlabs.ru,
	Scott Cheloha <cheloha@linux.ibm.com>,
	vaishnavi@linux.ibm.com, npiggin@gmail.com, tzungbi@kernel.org,
	brking@linux.ibm.com, linuxppc-dev@lists.ozlabs.org,
	linux@roeck-us.net
Subject: Re: [PATCH v2 3/4] powerpc/pseries: register pseries-wdt device with platform bus
Date: Fri, 24 Jun 2022 23:27:36 +1000	[thread overview]
Message-ID: <87v8sq42ev.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <874k0enied.fsf@linux.ibm.com>

Nathan Lynch <nathanl@linux.ibm.com> writes:
> Scott Cheloha <cheloha@linux.ibm.com> writes:
>> PAPR v2.12 defines a new hypercall, H_WATCHDOG.  The hypercall permits
>> guest control of one or more virtual watchdog timers.
...
>
> Seems like we don't need pseries_wdt_pdev as it's unused elsewhere? But
> that's quite minor.

It's minor but please drop it in the next version.

cheers

  reply	other threads:[~2022-06-24 13:27 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-02 17:53 [PATCH v2 0/4] pseries-wdt: initial support for H_WATCHDOG-based watchdog timers Scott Cheloha
2022-06-02 17:53 ` Scott Cheloha
2022-06-02 17:53 ` [PATCH v2 1/4] powerpc/pseries: hvcall.h: add H_WATCHDOG opcode, H_NOOP return code Scott Cheloha
2022-06-02 17:53   ` Scott Cheloha
2022-06-21 14:44   ` Nathan Lynch
2022-06-21 14:44     ` Nathan Lynch
2022-06-21 17:31     ` Segher Boessenkool
2022-06-21 17:31       ` Segher Boessenkool
2022-06-21 22:22       ` Nathan Lynch
2022-06-21 22:22         ` Nathan Lynch
2022-06-02 17:53 ` [PATCH v2 2/4] powerpc/pseries: add FW_FEATURE_WATCHDOG flag Scott Cheloha
2022-06-02 17:53   ` Scott Cheloha
2022-06-21 15:03   ` Nathan Lynch
2022-06-21 15:03     ` Nathan Lynch
2022-06-02 17:53 ` [PATCH v2 3/4] powerpc/pseries: register pseries-wdt device with platform bus Scott Cheloha
2022-06-02 17:53   ` Scott Cheloha
2022-06-21 15:30   ` Nathan Lynch
2022-06-24 13:27     ` Michael Ellerman [this message]
2022-07-07 15:53       ` Scott Cheloha
2022-07-07 15:53         ` Scott Cheloha
2022-06-02 17:53 ` [PATCH v2 4/4] watchdog/pseries-wdt: initial support for H_WATCHDOG-based watchdog timers Scott Cheloha
2022-06-02 17:53   ` Scott Cheloha
2022-06-20  6:09   ` Alexey Kardashevskiy
2022-06-20  6:09     ` Alexey Kardashevskiy
2022-06-21 15:45   ` Nathan Lynch
2022-06-21 15:45     ` Nathan Lynch
2022-06-24 13:27   ` Michael Ellerman
2022-06-24 15:31     ` Segher Boessenkool
2022-06-24 15:31       ` Segher Boessenkool
2022-07-08  5:51     ` Scott Cheloha
2022-07-08  5:51       ` Scott Cheloha
2022-06-24 13:51   ` Michael Ellerman
2022-07-07 15:53     ` Scott Cheloha
2022-07-07 15:53       ` Scott Cheloha
2022-06-16  1:43 ` [PATCH v2 0/4] pseries-wdt: " Daniel Henrique Barboza
2022-06-16 16:44   ` Tyrel Datwyler
2022-06-16 18:16     ` Daniel Henrique Barboza
2022-06-16 18:33   ` Daniel Henrique Barboza
2022-06-17 12:54 ` Daniel Henrique Barboza

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=87v8sq42ev.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.