From: Dinh Nguyen <dinguyen@kernel.org>
To: gregkh@linuxfoundation.org
Cc: dinguyen@kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] firmware: stratix10-svc: fixes for v7.1
Date: Thu, 28 May 2026 13:43:52 -0500 [thread overview]
Message-ID: <20260528184352.129179-1-dinguyen@kernel.org> (raw)
Hi Greg,
I based this on your char-misc-next branch that is at v7.1-rc3. I think that
is the correct procedure.
Thanks,
Dinh
The following changes since commit 5d6919055dec134de3c40167a490f33c74c12581:
Linux 7.1-rc3 (2026-05-10 14:08:09 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/dinguyen/linux.git tags/svc_fixes_for_v7.1
for you to fetch changes up to bfd2eb9bba548a8f63c3339bb1fb9a2031a42d86:
firmware: stratix10-rsu: Fix NULL deref on rsu_send_msg() timeout in probe (2026-05-28 13:34:07 -0500)
----------------------------------------------------------------
firmware: stratix10-svc and stratix10-rsu: fixes for v7.1
- Return -EOPNOTSUPP when ATF async is not supported
- Fix SVC driver from loading entirely when asynchronous ops is not
supported in older ATF.
- Fix a NULL pointer dereference on a timeout in rsu_send_msg()
----------------------------------------------------------------
Dinh Nguyen (1):
firmware: stratix10-rsu: Fix NULL deref on rsu_send_msg() timeout in probe
Muhammad Amirul Asyraf Mohamad Jamian (2):
firmware: stratix10-svc: Return -EOPNOTSUPP when ATF async unsupported
firmware: stratix10-svc: Don't fail probe when async ops unsupported
drivers/firmware/stratix10-rsu.c | 45 ++++++++++++++++++----------------------
drivers/firmware/stratix10-svc.c | 21 +++++++++++++++----
2 files changed, 37 insertions(+), 29 deletions(-)
next reply other threads:[~2026-05-28 18:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-28 18:43 Dinh Nguyen [this message]
2026-06-05 15:17 ` 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=20260528184352.129179-1-dinguyen@kernel.org \
--to=dinguyen@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®