mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Enrico Weigelt, metux IT consult" <info@metux.net>
To: linux-kernel@vger.kernel.org
Cc: axboe@kernel.dk, herbert@gondor.apana.org.au,
	davem@davemloft.net, linux-block@vger.kernel.org,
	linux-crypto@vger.kernel.org
Subject: [PATCH 1/3] mod_devicetable: helper macro for declaring oftree module device table
Date: Fri, 31 May 2019 13:54:48 +0200	[thread overview]
Message-ID: <1559303690-8108-2-git-send-email-info@metux.net> (raw)
In-Reply-To: <1559303690-8108-1-git-send-email-info@metux.net>

Little helper macro that declares an oftree module device table,
if CONFIG_OF is enabled. Otherwise it's just noop. Helpful for
reducing the number of #ifdef's.

Instead of:
    MODULE_DEVICE_TABLE(of, foo)
now use:
    MODULE_OF_TABLE(foo)

Signed-off-by: Enrico Weigelt <info@metux.net>
---
 include/linux/mod_devicetable.h | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/include/linux/mod_devicetable.h b/include/linux/mod_devicetable.h
index 448621c..0551b53 100644
--- a/include/linux/mod_devicetable.h
+++ b/include/linux/mod_devicetable.h
@@ -245,6 +245,15 @@ struct of_device_id {
 	const void *data;
 };
 
+/*
+ * macro for adding the of module device table only if CONFIG_OF enabled
+ */
+#ifdef CONFIG_OF
+#define MODULE_OF_TABLE(name)	MODULE_DEVICE_TABLE(of,name)
+#else
+#define MODULE_OF_TABLE(name)
+#endif /* CONFIG_OF */
+
 /* VIO */
 struct vio_device_id {
 	char type[32];
-- 
1.9.1


  reply	other threads:[~2019-05-31 11:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-31 11:54 RFC: get rid of #ifdef CONFIG_OF's around of match tables Enrico Weigelt, metux IT consult
2019-05-31 11:54 ` Enrico Weigelt, metux IT consult [this message]
2019-05-31 11:54 ` [PATCH 2/3] drivers: block: xsysace: use MODULE_OF_TABLE() and of_match_ptr() Enrico Weigelt, metux IT consult
2019-05-31 11:54 ` [PATCH 3/3] drivers: crypto: picoxcell_crypto: use MODULE_OF_TABLE() Enrico Weigelt, metux IT consult

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=1559303690-8108-2-git-send-email-info@metux.net \
    --to=info@metux.net \
    --cc=axboe@kernel.dk \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®