From: Guanbing Huang <albanhuang@outlook.com>
To: gregkh@linuxfoundation.org, andriy.shevchenko@intel.com,
rafael.j.wysocki@intel.com
Cc: linux-acpi@vger.kernel.org, tony@atomide.com,
john.ogness@linutronix.de, yangyicong@hisilicon.com,
jirislaby@kernel.org, linux-kernel@vger.kernel.org,
linux-serial@vger.kernel.org, lvjianmin@loongson.cn,
albanhuang@tencent.com, tombinfan@tencent.com
Subject: [PATCH v4 1/3] pnp: Add dev_is_pnp() macro
Date: Wed, 3 Apr 2024 15:41:28 +0800 [thread overview]
Message-ID: <PSAPR06MB4952DCB31578A5CB547612E3C93D2@PSAPR06MB4952.apcprd06.prod.outlook.com> (raw)
In-Reply-To: <20240403074130.93811-1-albanhuang@outlook.com>
From: Guanbing Huang <albanhuang@tencent.com>
Add dev_is_pnp() macro to determine whether the device is a pnp device.
Signed-off-by: Guanbing Huang <albanhuang@tencent.com>
Reviewed-by: Bing Fan <tombinfan@tencent.com>
Tested-by: Linheng Du <dylanlhdu@tencent.com>
---
include/linux/pnp.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include/linux/pnp.h b/include/linux/pnp.h
index ddbe7c3ca4ce..792921c06594 100644
--- a/include/linux/pnp.h
+++ b/include/linux/pnp.h
@@ -502,6 +502,8 @@ static inline void pnp_unregister_driver(struct pnp_driver *drv) { }
#endif /* CONFIG_PNP */
+#define dev_is_pnp(d) ((d)->bus == &pnp_bus_type)
+
/**
* module_pnp_driver() - Helper macro for registering a PnP driver
* @__pnp_driver: pnp_driver struct
--
2.17.1
next parent reply other threads:[~2024-04-03 7:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240403074130.93811-1-albanhuang@outlook.com>
2024-04-03 7:41 ` Guanbing Huang [this message]
2024-04-03 9:54 ` [PATCH v4 1/3] pnp: Add dev_is_pnp() macro Andy Shevchenko
2024-04-03 7:41 ` [PATCH v4 2/3] serial: 8250_port: Add support of pnp irq to __uart_read_properties() Guanbing Huang
2024-04-03 9:54 ` Andy Shevchenko
2024-04-03 10:06 ` Andy Shevchenko
2024-04-03 7:41 ` [PATCH v4 3/3] serial: 8250_pnp: Support configurable reg shift property Guanbing Huang
2024-04-03 10:00 ` Andy Shevchenko
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=PSAPR06MB4952DCB31578A5CB547612E3C93D2@PSAPR06MB4952.apcprd06.prod.outlook.com \
--to=albanhuang@outlook.com \
--cc=albanhuang@tencent.com \
--cc=andriy.shevchenko@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=john.ogness@linutronix.de \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=lvjianmin@loongson.cn \
--cc=rafael.j.wysocki@intel.com \
--cc=tombinfan@tencent.com \
--cc=tony@atomide.com \
--cc=yangyicong@hisilicon.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 read-only IMAP folder(s) and NNTP newsgroup(s).