[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5503DC94.1060405@gmail.com>
Date: Sat, 14 Mar 2015 00:00:36 -0700
From: Frank Rowand <frowand.list@...il.com>
To: Grant Likely <grant.likely@...aro.org>,
Rob Herring <robh+dt@...nel.org>,
Linux Kernel list <linux-kernel@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>
Subject: [Patch 3/5] dt: unittest: add const where needed
From: Frank Rowand <frank.rowand@...ymobile.com>
Fix warnings pointed out by checkpatch.
No bugs fixed, but the test code should be a good example of how to use
the devicetree API.
Signed-off-by: Frank Rowand <frank.rowand@...ymobile.com>
---
drivers/of/unittest.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
Index: b/drivers/of/unittest.c
===================================================================
--- a/drivers/of/unittest.c
+++ b/drivers/of/unittest.c
@@ -666,7 +666,7 @@ static void __init of_selftest_parse_int
of_node_put(np);
}
-static struct of_device_id match_node_table[] = {
+static const struct of_device_id match_node_table[] = {
{ .data = "A", .name = "name0", }, /* Name alone is lowest priority */
{ .data = "B", .type = "type1", }, /* followed by type alone */
@@ -740,7 +740,7 @@ static void __init of_selftest_platform_
int irq, rc;
struct device_node *np, *child, *grandchild;
struct platform_device *pdev;
- struct of_device_id match[] = {
+ const struct of_device_id match[] = {
{ .compatible = "test-device", },
{}
};
@@ -941,7 +941,7 @@ static int selftest_remove(struct platfo
return 0;
}
-static struct of_device_id selftest_match[] = {
+static const struct of_device_id selftest_match[] = {
{ .compatible = "selftest", },
{},
};
@@ -1533,7 +1533,7 @@ static int selftest_i2c_bus_remove(struc
return 0;
}
-static struct of_device_id selftest_i2c_bus_match[] = {
+static const struct of_device_id selftest_i2c_bus_match[] = {
{ .compatible = "selftest-i2c-bus", },
{},
};
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists