All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: stable <stable@vger.kernel.org>,
	Frank Rowand <frank.rowand@sony.com>,
	Alan Tull <atull@kernel.org>,
	Michael Ellerman <mpe@ellerman.id.au>
Subject: Re: devicetree patches for v4.19.y, v4.20.y
Date: Mon, 4 Feb 2019 09:52:16 +0100	[thread overview]
Message-ID: <20190204085216.GA2015@kroah.com> (raw)
In-Reply-To: <d34badba-1764-5bde-377b-34c65dd4ba30@roeck-us.net>

On Sat, Feb 02, 2019 at 01:20:13PM -0800, Guenter Roeck wrote:
> Hi,
> 
> some of my boot tests in v4.19.y and v4.20.y currently generate tracebacks
> as announced in commit 7c528e457d53 ("of: overlay: add missing of_node_put()
> after add new node to changeset"). This commit has been applied to both
> stable releases. The following patch series fixes the problem.
> 
> v4.19.y:
> 
> a613b26a5013 of: Convert to using %pOFn instead of device_node.name
> 144552c78692 of: overlay: add tests to validate kfrees from overlay removal
> 5b2c2f5a0ea3 of: overlay: add missing of_node_get() in __of_attach_node_sysfs
> 6b4955ba7bc0 of: overlay: use prop add changeset entry for property in new nodes
> 8814dc46bd9e of: overlay: do not duplicate properties from overlay for new nodes
> 
> v4.20.y:
> 
> 144552c78692 of: overlay: add tests to validate kfrees from overlay removal
> 5b2c2f5a0ea3 of: overlay: add missing of_node_get() in __of_attach_node_sysfs
> 6b4955ba7bc0 of: overlay: use prop add changeset entry for property in new nodes
> 8814dc46bd9e of: overlay: do not duplicate properties from overlay for new nodes
> 
> Not all of those patches fix bugs, but they are required for the series
> to apply cleanly.
> 
> Please consider applying the above patches to both releases.

All now queued up, thanks!

greg k-h

      reply	other threads:[~2019-02-04  8:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-02 21:20 devicetree patches for v4.19.y, v4.20.y Guenter Roeck
2019-02-04  8:52 ` Greg Kroah-Hartman [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=20190204085216.GA2015@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=atull@kernel.org \
    --cc=frank.rowand@sony.com \
    --cc=linux@roeck-us.net \
    --cc=mpe@ellerman.id.au \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.