From: Quentin Perret <qperret@google.com>
To: stable@vger.kernel.org
Cc: alexandre.torgue@foss.st.com, robh+dt@kernel.org,
f.fainelli@gmail.com, ardb@kernel.org,
gregkh@linuxfoundation.org, sashal@kernel.org
Subject: Revert memblock backports with missing dependencies
Date: Wed, 12 May 2021 12:28:51 +0000 [thread overview]
Message-ID: <20210512122853.3243417-1-qperret@google.com> (raw)
Hi all,
A breakage in 5.4.102 has been reported [1] due to the backport of the
two following upstream commits:
8a5a75e5e9e5 ("of/fdt: Make sure no-map does not remove already reserved regions")
86588296acbf ("fdt: Properly handle "no-map" field in the memory region")
As Alexandre noted in the original thread, the backport missed
dependencies. But since these patches were not really fixes in the first
place, it seems preferable to simply revert them from 5.4 and earlier.
[1] https://lore.kernel.org/linux-arm-kernel/CAL_Jsq+LUPZFhXd+j-xM67rZB=pvEvZM+1sfckip0Lqq02PkZQ@mail.gmail.com/
Quentin Perret (2):
Revert "of/fdt: Make sure no-map does not remove already reserved
regions"
Revert "fdt: Properly handle "no-map" field in the memory region"
drivers/of/fdt.c | 12 ++----------
1 file changed, 2 insertions(+), 10 deletions(-)
--
2.31.1.607.g51e8a6a459-goog
next reply other threads:[~2021-05-12 12:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-12 12:28 Quentin Perret [this message]
2021-05-12 12:28 ` [PATCH stable 5.4 1/2] Revert "of/fdt: Make sure no-map does not remove already reserved regions" Quentin Perret
2021-05-12 12:28 ` [PATCH stable 5.4 2/2] Revert "fdt: Properly handle "no-map" field in the memory region" Quentin Perret
2021-05-12 12:30 ` [PATCH stable 4.19 1/2] Revert "of/fdt: Make sure no-map does not remove already reserved regions" Quentin Perret
2021-05-12 12:30 ` [PATCH stable 4.19 2/2] Revert "fdt: Properly handle "no-map" field in the memory region" Quentin Perret
2021-05-12 12:30 ` [PATCH stable 4.14 1/2] Revert "of/fdt: Make sure no-map does not remove already reserved regions" Quentin Perret
2021-05-12 12:30 ` [PATCH stable 4.14 2/2] Revert "fdt: Properly handle "no-map" field in the memory region" Quentin Perret
2021-05-12 12:30 ` [PATCH stable 4.9 1/2] Revert "of/fdt: Make sure no-map does not remove already reserved regions" Quentin Perret
2021-05-12 12:30 ` [PATCH stable 4.9 2/2] Revert "fdt: Properly handle "no-map" field in the memory region" Quentin Perret
2021-05-12 12:34 ` Revert memblock backports with missing dependencies Ard Biesheuvel
2021-05-12 14:07 ` Greg KH
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=20210512122853.3243417-1-qperret@google.com \
--to=qperret@google.com \
--cc=alexandre.torgue@foss.st.com \
--cc=ardb@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=robh+dt@kernel.org \
--cc=sashal@kernel.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