From: Kevin Hilman <khilman@baylibre.com>
To: Christian Hewitt <christianshewitt@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Neil Armstrong <narmstrong@baylibre.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: Christian Hewitt <christianshewitt@gmail.com>
Subject: Re: [PATCH 0/3] arm64: dts: meson: add ATF BL32 reserved-memory regions
Date: Tue, 01 Feb 2022 11:04:29 -0800 [thread overview]
Message-ID: <7hr18m9znm.fsf@baylibre.com> (raw)
In-Reply-To: <20220126044954.19069-1-christianshewitt@gmail.com>
Christian Hewitt <christianshewitt@gmail.com> writes:
> This series supersedes [0] which fixed a long-running kernel panic issue
> seen with Beelink G12B devices booted from Amlogic vendor firmware. The
> same issue exists with a wider set of devices from GXBB to SM1, although
> it is not often seen due to my kernel fork including 'catch-all' patches
> for some time (the meson-gx patch was suggested by Matheusz in 2019) and
> many distros actively supporting Amlogic hardware consuming some or all
> of my regular patchset.
>
> I've also included a cleanup to the SEI510/SEI610 board files. If that's
> not desirable feel free to ignore that patch. I also dropped the fixes
> tagging as I'm not sure what original commits could be targetted. If you
> think fixes are good please provide some guidance and I'll be happy to
> send a revised series.
Reviewed-by: Kevin Hilman <khilman@baylibre.com>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-02-01 19:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 4:49 [PATCH 0/3] arm64: dts: meson: add ATF BL32 reserved-memory regions Christian Hewitt
2022-01-26 4:49 ` [PATCH 1/3] arm64: dts: meson-gx: add ATF BL32 reserved-memory region Christian Hewitt
2022-01-26 5:35 ` Vyacheslav
2022-01-26 7:12 ` Christian Hewitt
2022-01-27 10:44 ` Neil Armstrong
2022-01-27 10:46 ` Neil Armstrong
2022-01-26 4:49 ` [PATCH 2/3] arm64: dts: meson-g12: " Christian Hewitt
2022-01-27 10:46 ` Neil Armstrong
2022-01-26 4:49 ` [PATCH 3/3] arm64: dts: meson-g12: drop BL32 region from SEI510/SEI610 Christian Hewitt
2022-01-27 10:46 ` Neil Armstrong
2022-02-01 19:04 ` Kevin Hilman [this message]
2022-02-04 8:23 ` [PATCH 0/3] arm64: dts: meson: add ATF BL32 reserved-memory regions Neil Armstrong
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=7hr18m9znm.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=christianshewitt@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=narmstrong@baylibre.com \
--cc=robh+dt@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).