From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Phil Elwell <phil@raspberrypi.org>
Cc: stable@vger.kernel.org
Subject: Re: Dynamic overlay failure in 4.19 & 4.20
Date: Wed, 5 Jun 2019 19:50:59 +0200 [thread overview]
Message-ID: <20190605175059.GA29747@kroah.com> (raw)
In-Reply-To: <2da582d1-11eb-3680-33f2-3a5c139613a8@raspberrypi.org>
On Wed, Jun 05, 2019 at 01:02:18PM +0100, Phil Elwell wrote:
> Hi,
>
> I think patch f96278810150 ("of: overlay: set node fields from
> properties when add new overlay node") should be back-ported to 4.19,
> for the reasons outlined below (briefly: without it, overlay fragments
> that define phandles will appear to merged successfully, but they do
> so without those phandles, causing any references to them to break).
That patch does not properly apply to the 4.19.y tree. Can you provide
a working backport that I can queue up to resolve this?
thanks,
greg k-h
next prev parent reply other threads:[~2019-06-05 17:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <45e99a24-efb9-5473-2e57-14411537dc9f@raspberrypi.org>
2019-06-05 12:02 ` Dynamic overlay failure in 4.19 & 4.20 Phil Elwell
2019-06-05 17:50 ` Greg Kroah-Hartman [this message]
2019-06-05 18:36 ` Phil Elwell
2019-06-06 1:14 ` Sasha Levin
2019-06-06 19:54 ` Greg Kroah-Hartman
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=20190605175059.GA29747@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=phil@raspberrypi.org \
--cc=stable@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).