From: Alexander Grund <theflamefire89@gmail.com>
To: cip-dev@lists.cip-project.org
Cc: uli+cip@fpond.eu
Subject: [PATCH 4.4 0/1] Fix null pointer deref
Date: Sun, 23 Mar 2025 09:21:17 +0100 [thread overview]
Message-ID: <20250323082118.8153-1-theflamefire89@gmail.com> (raw)
From: Alexander Grund <flamefire89@gmail.com>
The patch
"can: sun4i_can: sun4i_can_err(): call can_change_state() even if cf is NULL"
assumes the following patch which isn't applied yet to cip-4.4
Marc Kleine-Budde (1):
can: dev: make can_change_state() robust to be called with cf == NULL
drivers/net/can/dev.c | 3 +++
1 file changed, 3 insertions(+)
--
2.40.1
next reply other threads:[~2025-03-23 8:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-23 8:21 Alexander Grund [this message]
2025-03-23 8:21 ` [PATCH 4.4 1/1] can: dev: make can_change_state() robust to be called with cf == NULL Alexander Grund
2025-03-27 12:57 ` [PATCH 4.4 0/1] Fix null pointer deref Ulrich Hecht
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=20250323082118.8153-1-theflamefire89@gmail.com \
--to=theflamefire89@gmail.com \
--cc=cip-dev@lists.cip-project.org \
--cc=uli+cip@fpond.eu \
/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