From: Conor Dooley <conor@kernel.org>
To: soc@kernel.org
Cc: conor@kernel.org, palmer@dabbelt.com, linux-riscv@lists.infradead.org
Subject: [GIT PULL] RISC-V firmware drivers for v6.9
Date: Tue, 5 Mar 2024 20:00:42 +0000 [thread overview]
Message-ID: <20240305-vicinity-dumpling-8943ef26f004@spud> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1192 bytes --]
Hey Arnd,
Feel free to cherry pick this either if it makes more sense (or even
send it to fixes instead). It's a fix for an oversize allocation, so
given how late it is in the merge window I opted to send it as 6.9
material.
Cheers,
Conor.
The following changes since commit 6613476e225e090cc9aad49be7fa504e290dd33d:
Linux 6.8-rc1 (2024-01-21 14:11:32 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/conor/linux.git/ riscv-firmware-for-v6.9
for you to fetch changes up to af1e0a7d39f98c0dea1b186a76fcee7da6a5f7bc:
firmware: microchip: Fix over-requested allocation size (2024-03-04 19:18:16 +0000)
----------------------------------------------------------------
RISC-V firmware drivers for v6.9
A single minor fix for an oversized allocation due to sizeof() misuse by
yours truly that came in since I sent my last fixes PR.
Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
----------------------------------------------------------------
Dawei Li (1):
firmware: microchip: Fix over-requested allocation size
drivers/firmware/microchip/mpfs-auto-update.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 161 bytes --]
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
reply other threads:[~2024-03-05 20:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240305-vicinity-dumpling-8943ef26f004@spud \
--to=conor@kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=soc@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).