From: Philipp Zabel <p.zabel@pengutronix.de>
To: Ronald Claveau <linux-kernel-dev@aliel.fr>,
Neil Armstrong <neil.armstrong@linaro.org>,
Kevin Hilman <khilman@baylibre.com>,
Jerome Brunet <jbrunet@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] reset: amlogic: t7: Fix null reset ops
Date: Tue, 31 Mar 2026 17:25:43 +0200 [thread overview]
Message-ID: <f619c0b56d94ac666bb8914d0740e2f905c0e347.camel@pengutronix.de> (raw)
In-Reply-To: <20260331-fix-aml-t7-null-reset-v1-1-eb95b625234c@aliel.fr>
On Di, 2026-03-31 at 16:24 +0200, Ronald Claveau wrote:
> Fix missing reset ops causing kernel null pointer dereference.
> This SOC's reset is currently not used yet.
>
> Signed-off-by: Ronald Claveau <linux-kernel-dev@aliel.fr>
Applied to reset/fixes, thanks!
[1/2] reset: amlogic: t7: Fix null reset ops
https://git.pengutronix.de/cgit/pza/linux/commit/?id=9797524ef2b6
regards
Philipp
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2026-03-31 15:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 14:24 [PATCH 0/2] Fix Amlogic T7 null reset ops and DT required property Ronald Claveau
2026-03-31 14:24 ` [PATCH 1/2] reset: amlogic: t7: Fix null reset ops Ronald Claveau
2026-03-31 14:54 ` Philipp Zabel
2026-03-31 15:25 ` Philipp Zabel [this message]
2026-03-31 14:24 ` [PATCH 2/2] arm64: dts: amlogic: t7: Fix missing required reset property Ronald Claveau
2026-05-13 12:37 ` (subset) " Neil Armstrong
2026-04-08 9:10 ` (subset) [PATCH 0/2] Fix Amlogic T7 null reset ops and DT required property 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=f619c0b56d94ac666bb8914d0740e2f905c0e347.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel-dev@aliel.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=neil.armstrong@linaro.org \
--cc=robh@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
all inboxes | Powered by JetHome®