All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Cheloha <cheloha@linux.ibm.com>
To: linux-watchdog@vger.kernel.org
Cc: linux@roeck-us.net, 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: [PATCH v1 0/4] pseries-wdt: initial support for PAPR virtual watchdog timers
Date: Fri, 20 May 2022 13:35:48 -0500	[thread overview]
Message-ID: <20220520183552.33426-1-cheloha@linux.ibm.com> (raw)

This series is preceded by two RFCs:

RFC v1: https://lore.kernel.org/linux-watchdog/20220413165104.179144-1-cheloha@linux.ibm.com/
RFC v2: https://lore.kernel.org/linux-watchdog/20220509174357.5448-1-cheloha@linux.ibm.com/

Changes of note from RFC v2:

- Separate platform device registration in pseries/setup.c into a
  separate patch to avoid cross-subsystem patches.

- Change the "action" module parameter to use integers instead of
  strings.

- Add a proper .get method, action_get(), for reading the "action"
  module parameter value.

- Document pseries-wdt module parameters in watchdog-parameters.rst.

- Correct many checkpatch.pl warnings.

- For now, assume there is only one pseries-wdt device and always
  assign it watchdogNumber 1.



WARNING: multiple messages have this Message-ID (diff)
From: Scott Cheloha <cheloha@linux.ibm.com>
To: linux-watchdog@vger.kernel.org
Cc: nathanl@linux.ibm.com, wvoigt@us.ibm.com, aik@ozlabs.ru,
	vaishnavi@linux.ibm.com, npiggin@gmail.com, tzungbi@kernel.org,
	brking@linux.ibm.com, linuxppc-dev@lists.ozlabs.org,
	linux@roeck-us.net
Subject: [PATCH v1 0/4] pseries-wdt: initial support for PAPR virtual watchdog timers
Date: Fri, 20 May 2022 13:35:48 -0500	[thread overview]
Message-ID: <20220520183552.33426-1-cheloha@linux.ibm.com> (raw)

This series is preceded by two RFCs:

RFC v1: https://lore.kernel.org/linux-watchdog/20220413165104.179144-1-cheloha@linux.ibm.com/
RFC v2: https://lore.kernel.org/linux-watchdog/20220509174357.5448-1-cheloha@linux.ibm.com/

Changes of note from RFC v2:

- Separate platform device registration in pseries/setup.c into a
  separate patch to avoid cross-subsystem patches.

- Change the "action" module parameter to use integers instead of
  strings.

- Add a proper .get method, action_get(), for reading the "action"
  module parameter value.

- Document pseries-wdt module parameters in watchdog-parameters.rst.

- Correct many checkpatch.pl warnings.

- For now, assume there is only one pseries-wdt device and always
  assign it watchdogNumber 1.



             reply	other threads:[~2022-05-20 18:37 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-20 18:35 Scott Cheloha [this message]
2022-05-20 18:35 ` [PATCH v1 0/4] pseries-wdt: initial support for PAPR virtual watchdog timers Scott Cheloha
2022-05-20 18:35 ` [PATCH v1 1/4] powerpc/pseries: hvcall.h: add H_WATCHDOG opcode, H_NOOP return code Scott Cheloha
2022-05-20 18:35   ` Scott Cheloha
2022-05-20 18:35 ` [PATCH v1 2/4] powerpc/pseries: add FW_FEATURE_WATCHDOG flag Scott Cheloha
2022-05-20 18:35   ` Scott Cheloha
2022-05-20 18:35 ` [PATCH v1 3/4] powerpc/pseries: register pseries-wdt device with platform bus Scott Cheloha
2022-05-20 18:35   ` Scott Cheloha
2022-05-20 18:35 ` [PATCH v1 4/4] watchdog/pseries-wdt: initial support for PAPR H_WATCHDOG timers Scott Cheloha
2022-05-20 18:35   ` Scott Cheloha
2022-05-25  6:35   ` Alexey Kardashevskiy
2022-05-25  6:35     ` Alexey Kardashevskiy
2022-05-25  7:52     ` Guenter Roeck
2022-05-25  7:52       ` Guenter Roeck
2022-06-01 15:07       ` Scott Cheloha
2022-06-01 15:07         ` Scott Cheloha
2022-06-01 15:45         ` Guenter Roeck
2022-06-01 15:45           ` Guenter Roeck
2022-06-01 15:56           ` Scott Cheloha
2022-06-01 15:56             ` Scott Cheloha
2022-06-01 14:48     ` Scott Cheloha
2022-06-01 14:48       ` Scott Cheloha
2022-06-02  4:27       ` Alexey Kardashevskiy
2022-06-02  4:27         ` Alexey Kardashevskiy

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=20220520183552.33426-1-cheloha@linux.ibm.com \
    --to=cheloha@linux.ibm.com \
    --cc=aik@ozlabs.ru \
    --cc=brking@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.