diff options
| author | Douglas Anderson <[email protected]> | 2022-04-29 16:43:47 -0700 |
|---|---|---|
| committer | Rafael J. Wysocki <[email protected]> | 2022-05-05 14:19:15 +0200 |
| commit | 117ef574074d69d87c222dbbbc744bc06cf5a833 (patch) | |
| tree | 59fd7f3c6488fed347dec4ef5d98e7fca60a3d2f /lib/test_fortify/write_overflow-memcpy.c | |
| parent | 022fe6bc8f3bd0f2b1f9bc778bacc38020dfd420 (diff) | |
device property: Fix recent breakage of fwnode_get_next_parent_dev()
Due to a subtle typo, instead of commit 87ffea09470d ("device
property: Introduce fwnode_for_each_parent_node()") being a no-op
change, it ended up causing the display on my sc7180-trogdor-lazor
device from coming up unless I added "fw_devlink=off" to my kernel
command line. Fix the typo.
Fixes: 87ffea09470d ("device property: Introduce fwnode_for_each_parent_node()")
Signed-off-by: Douglas Anderson <[email protected]>
Reviewed-by: Saravana Kannan <[email protected]>
Reviewed-by: Sakari Ailus <[email protected]>
Reviewed-by: Andy Shevchenko <[email protected]>
Signed-off-by: Rafael J. Wysocki <[email protected]>
Diffstat (limited to 'lib/test_fortify/write_overflow-memcpy.c')
0 files changed, 0 insertions, 0 deletions