From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: linux-watchdog@vger.kernel.org
Cc: linux-renesas-soc@vger.kernel.org,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
Wolfram Sang <wsa+renesas@sang-engineering.com>
Subject: [RFC PATCH v2 3/4] watchdog: core: add module_watchdog_pci_driver()
Date: Tue, 28 Aug 2018 21:14:15 +0200 [thread overview]
Message-ID: <20180828191416.7781-4-wsa+renesas@sang-engineering.com> (raw)
In-Reply-To: <20180828191416.7781-1-wsa+renesas@sang-engineering.com>
Allow PCI drivers to prevent removing if NOWAYOUT, too.
Note: This is only a build-tested proof-of-concept!
Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
---
include/linux/watchdog.h | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/include/linux/watchdog.h b/include/linux/watchdog.h
index 5768fb6b5cde..07c01e8050e8 100644
--- a/include/linux/watchdog.h
+++ b/include/linux/watchdog.h
@@ -236,4 +236,8 @@ module_exit(__driver##_exit)
module_watchdog_driver(__platform_driver, platform_driver_register, \
platform_driver_unregister, __nowayout)
+#define module_watchdog_pci_driver(__pci_driver, __nowayout) \
+ module_watchdog_driver(__pci_driver, pci_register_driver, \
+ pci_unregister_driver, __nowayout)
+
#endif /* ifndef _LINUX_WATCHDOG_H */
--
2.11.0
next prev parent reply other threads:[~2018-08-28 23:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-28 19:14 [RFC PATCH v2 0/4] watchdog: prevent removing a driver if NOWAYOUT Wolfram Sang
2018-08-28 19:14 ` [RFC PATCH v2 1/4] watchdog: core: add mechanism to prevent removing " Wolfram Sang
2018-08-28 19:33 ` Guenter Roeck
2018-08-28 20:07 ` Wolfram Sang
2018-08-28 20:47 ` Guenter Roeck
2018-08-28 19:14 ` [RFC PATCH v2 2/4] watchdog: renesas_wdt: avoid " Wolfram Sang
2018-08-28 19:14 ` Wolfram Sang [this message]
2018-08-28 19:14 ` [RFC PATCH v2 4/4] watchdog: i6300esb: " Wolfram Sang
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=20180828191416.7781-4-wsa+renesas@sang-engineering.com \
--to=wsa+renesas@sang-engineering.com \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=yoshihiro.shimoda.uh@renesas.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).