Messages in this thread | | | Date | Sat, 14 May 2022 07:47:15 +0200 | From | Greg Kroah-Hartman <> | Subject | Re: [PATCH] device property: Fix recent breakage of fwnode_get_next_parent_dev() |
| |
On Fri, May 13, 2022 at 08:58:12PM -0700, Saravana Kannan wrote: > On Thu, May 5, 2022 at 5:21 AM Rafael J. Wysocki <rafael@kernel.org> wrote: > > > > On Sun, May 1, 2022 at 9:50 AM Andy Shevchenko > > <andy.shevchenko@gmail.com> wrote: > > > > > > On Sat, Apr 30, 2022 at 3:00 PM Douglas Anderson <dianders@chromium.org> wrote: > > > > > > > > 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. > > > > > > Sorry and merci pour la fix! > > > Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com> > > > > Applied, thanks! > > Has this been picked up by one of the driver-core branches yet? I was > poking around that > git repo and didn't see any commit with this title. This breaks > fw_devlink in a severe manner, so I want to make sure it gets into > 5.18.
Look in linux-next: 117ef574074d ("device property: Fix recent breakage of fwnode_get_next_parent_dev()")
Rafael's tree is not my tree :)
thanks,
greg k-h
| |