From: <gregkh@linuxfoundation.org>
To: javier@osg.samsung.com, gregkh@linuxfoundation.org,
pali.rohar@gmail.com, tony@atomide.com
Cc: <stable@vger.kernel.org>, <stable-commits@vger.kernel.org>
Subject: Patch "ARM: dts: am33xx: Add an empty chosen node to top level DTSI" has been added to the 4.9-stable tree
Date: Mon, 23 Jan 2017 17:02:18 +0100 [thread overview]
Message-ID: <148518733887151@kroah.com> (raw)
This is a note to let you know that I've just added the patch titled
ARM: dts: am33xx: Add an empty chosen node to top level DTSI
to the 4.9-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
arm-dts-am33xx-add-an-empty-chosen-node-to-top-level-dtsi.patch
and it can be found in the queue-4.9 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@vger.kernel.org> know about it.
>From 1d8d6d3f2f7d553c479f24ab93767974a8c2dfad Mon Sep 17 00:00:00 2001
From: Javier Martinez Canillas <javier@osg.samsung.com>
Date: Mon, 19 Dec 2016 11:44:37 -0300
Subject: ARM: dts: am33xx: Add an empty chosen node to top level DTSI
From: Javier Martinez Canillas <javier@osg.samsung.com>
commit 1d8d6d3f2f7d553c479f24ab93767974a8c2dfad upstream.
Commit f8bf01611c99 ("ARM: dts: am33xx: Remove skeleton.dtsi usage")
removed the skeleton.dtsi usage since we want to get rid of it.
But this can cause issues when booting a kernel with a boot-loader
that doesn't create a chosen node if this isn't present in the DTB
since the decompressor relies on a pre-existing chosen node to be
available to insert the command line and merge other ATAGS info.
Fixes: f8bf01611c99 ("ARM: dts: am33xx: Remove skeleton.dtsi usage")
Reported-by: Pali Rohar <pali.rohar@gmail.com>
Signed-off-by: Javier Martinez Canillas <javier@osg.samsung.com>
Signed-off-by: Tony Lindgren <tony@atomide.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
arch/arm/boot/dts/am33xx.dtsi | 1 +
1 file changed, 1 insertion(+)
--- a/arch/arm/boot/dts/am33xx.dtsi
+++ b/arch/arm/boot/dts/am33xx.dtsi
@@ -16,6 +16,7 @@
interrupt-parent = <&intc>;
#address-cells = <1>;
#size-cells = <1>;
+ chosen { };
aliases {
i2c0 = &i2c0;
Patches currently in stable-queue which might be from javier@osg.samsung.com are
queue-4.9/arm-dts-omap3-add-an-empty-chosen-node-to-top-level-dtsi.patch
queue-4.9/arm-dts-omap3-add-dts-for-logic-pd-som-lv-37xx-dev-kit.patch
queue-4.9/arm-dts-omap5-add-an-empty-chosen-node-to-top-level-dtsi.patch
queue-4.9/clocksource-exynos_mct-clear-interrupt-when-cpu-is-shut-down.patch
queue-4.9/arm-dts-omap2-add-an-empty-chosen-node-to-top-level-dtsi.patch
queue-4.9/arm-dts-am4372-add-an-empty-chosen-node-to-top-level-dtsi.patch
queue-4.9/arm-dts-dm816x-add-an-empty-chosen-node-to-top-level-dtsi.patch
queue-4.9/arm-dts-omap4-add-an-empty-chosen-node-to-top-level-dtsi.patch
queue-4.9/arm-dts-am33xx-add-an-empty-chosen-node-to-top-level-dtsi.patch
queue-4.9/arm-dts-dra7-add-an-empty-chosen-node-to-top-level-dtsi.patch
queue-4.9/arm-dts-dm814x-add-an-empty-chosen-node-to-top-level-dtsi.patch
reply other threads:[~2017-01-23 16:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=148518733887151@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=javier@osg.samsung.com \
--cc=pali.rohar@gmail.com \
--cc=stable-commits@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 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.