From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1] ARM:sunxi:sid: Make use of the of_match_ptr
Date: Wed, 07 Jan 2015 10:00:55 +0100 [thread overview]
Message-ID: <12820267.9PZueKuf7O@wuerfel> (raw)
In-Reply-To: <1420616468-3782-1-git-send-email-oliver+list@schinagl.nl>
On Wednesday 07 January 2015 08:41:08 Olliver Schinagl wrote:
> From: Olliver Schinagl <oliver@schinagl.nl>
>
> I probably have forgotten to use this macro for the of_match pointer, so
> this patch adds the of_match_ptr macro.
>
> Signed-off-by: Olliver Schinagl <oliver@schinagl.nl>
> ---
> drivers/misc/eeprom/sunxi_sid.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/misc/eeprom/sunxi_sid.c b/drivers/misc/eeprom/sunxi_sid.c
> index 8385177..5a330d9 100644
> --- a/drivers/misc/eeprom/sunxi_sid.c
> +++ b/drivers/misc/eeprom/sunxi_sid.c
> @@ -25,6 +25,7 @@
> #include <linux/kernel.h>
> #include <linux/kobject.h>
> #include <linux/module.h>
> +#include <linux/of.h>
> #include <linux/of_device.h>
> #include <linux/platform_device.h>
> #include <linux/random.h>
> @@ -146,7 +147,7 @@ static struct platform_driver sunxi_sid_driver = {
> .remove = sunxi_sid_remove,
> .driver = {
> .name = DRV_NAME,
> - .of_match_table = sunxi_sid_of_match,
> + .of_match_table = of_match_ptr(sunxi_sid_of_match),
> },
> };
> module_platform_driver(sunxi_sid_driver);
This looks wrong: sunxi_sid_of_match is defined unconditionally, so
now you get a compiler warning if CONFIG_OF is disabled.
The existing code is good, we only add the of_match_ptr() for drivers
that are useful without CONFIG_OF and that want to save a few bytes
in .data size.
Arnd
next prev parent reply other threads:[~2015-01-07 9:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-07 7:41 [PATCH v1] ARM:sunxi:sid: Make use of the of_match_ptr Olliver Schinagl
2015-01-07 8:49 ` Maxime Ripard
2015-01-07 9:00 ` Arnd Bergmann [this message]
2015-01-07 9:26 ` Olliver Schinagl
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=12820267.9PZueKuf7O@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.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