summaryrefslogtreecommitdiffstats
path: root/drivers/of
diff options
context:
space:
mode:
authorFrank Rowand <frank.rowand@sony.com>2018-10-04 20:30:40 -0700
committerFrank Rowand <frank.rowand@sony.com>2018-11-08 22:11:23 -0800
commit81225ea682f45629a66309636482b7c9bc2dcec1 (patch)
tree74343acd1d76081919a1f700cf1876de40d567ab /drivers/of
parent8814dc46bd9e347d4de55ec5bf8f16ea54470499 (diff)
downloadlinux-81225ea682f45629a66309636482b7c9bc2dcec1.tar.gz
linux-81225ea682f45629a66309636482b7c9bc2dcec1.tar.bz2
linux-81225ea682f45629a66309636482b7c9bc2dcec1.zip
of: overlay: reorder fields in struct fragment
Order the fields of struct fragment in the same order as struct of_overlay_notify_data. The order in struct fragment is not significant. If both structs are ordered the same then when examining the data in a debugger or dump the human involved does not have to remember which context they are examining. Tested-by: Alan Tull <atull@kernel.org> Signed-off-by: Frank Rowand <frank.rowand@sony.com>
Diffstat (limited to 'drivers/of')
-rw-r--r--drivers/of/overlay.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/of/overlay.c b/drivers/of/overlay.c
index 9808aae4621a..15be3da34fef 100644
--- a/drivers/of/overlay.c
+++ b/drivers/of/overlay.c
@@ -49,8 +49,8 @@ struct target {
* @overlay: pointer to the __overlay__ node
*/
struct fragment {
- struct device_node *target;
struct device_node *overlay;
+ struct device_node *target;
};
/**