Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Adam Ford <aford173@gmail.com>
Cc: stable <stable@vger.kernel.org>, Tony Lindgren <tony@atomide.com>,
	Linux-OMAP <linux-omap@vger.kernel.org>
Subject: Re: of: property: Simplify of_link_to_phandle()
Date: Thu, 7 Sep 2023 11:11:44 +0100	[thread overview]
Message-ID: <2023090715-charity-numerous-f6f0@gregkh> (raw)
In-Reply-To: <CAHCN7x+GLhYyEMq0h0Sa3m9JMuZf0g7=FpT==uFOg=w7OQ=qUw@mail.gmail.com>

On Wed, Sep 06, 2023 at 06:49:07PM -0500, Adam Ford wrote:
> Stable Group,
> 
> Please apply commit 4a032827daa8 ("of: property: Simplify of_link_to_phandle()")
> to the 6.1.y stable branch.  It was originally part of a series that
> was only partially applied to 6.1.  Being partially applied left 6.1.y
> in a state where a bunch of peripherals were deferred indefinitely on
> the am3517-evm.
> 
> wl12xx_buf platform: supplier 48002000.scm not ready
> wl12xx_vmmc2 platform: supplier wl12xx_buf not ready
> 48050000.dss platform: supplier display@0 not ready
> 48064800.ehci platform: supplier hsusb1_phy not ready
> backlight platform: supplier 48002000.scm not ready
> display@0 platform: supplier backlight not ready
> dmtimer-pwm@11 platform: supplier 48002000.scm not ready
> hsusb1_phy platform: supplier 48002000.scm not ready
> gpio-leds platform: supplier 48002000.scm not ready
> 480b4000.mmc platform: supplier wl12xx_vmmc2 not ready
> 
> With the above commit applied, it appears to address most of the
> deferred peripherals.
> 
> Fixes: eaf9b5612a47 ("driver core: fw_devlink: Don't purge child
> fwnode's consumer links")
> Signed-off-by:  Adam Ford <aford173@gmail.com>

Now queued up, thanks.

greg k-h

      reply	other threads:[~2023-09-07 15:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-06 23:49 of: property: Simplify of_link_to_phandle() Adam Ford
2023-09-07 10:11 ` Greg KH [this message]

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=2023090715-charity-numerous-f6f0@gregkh \
    --to=greg@kroah.com \
    --cc=aford173@gmail.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=tony@atomide.com \
    /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