All of lore.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: soc@kernel.org
Cc: conor@kernel.org, linux-riscv@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL][1/4] RISC-V firmware drivers for v7.4
Date: Tue, 13 Oct 2026 16:14:18 +0100	[thread overview]
Message-ID: <20261013-defame-busload-7eeb111f35ce@spud> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1217 bytes --]

Hey folks,

Might be my last mini PR here, since the RISC-V SSE driver is coming via
the actual RISC-V tree, so there'll almost certainly be a much increased
activity here going forwards.

I'm a bit late PR wise (sorry) but I blame conferences and a busy week
beforehand for that...

Thanks,
Conor.

The following changes since commit cee9395acd8043be0644b25c34bfa86623f2b935:

  Linux 7.3-rc1 (2026-08-30 13:34:40 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/conor/linux.git/ riscv-firmware-for-v7.4

for you to fetch changes up to 525e00a1bbced112f5431448842b27fa7621725f:

  firmware: microchip: use kzalloc_objs() instead of kzalloc() with multiply (2026-09-08 20:36:04 +0100)

----------------------------------------------------------------
RISC-V firmware drivers for v7.4

A single fix/cleanup for the auto update driver.

Signed-off-by: Conor Dooley <conor.dooley@microchip.com>

----------------------------------------------------------------
Hrushiraj Gandhi (1):
      firmware: microchip: use kzalloc_objs() instead of kzalloc() with multiply

 drivers/firmware/microchip/mpfs-auto-update.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

[-- 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

WARNING: multiple messages have this Message-ID (diff)
From: Conor Dooley <conor@kernel.org>
To: soc@kernel.org
Cc: conor@kernel.org, linux-riscv@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL][1/4] RISC-V firmware drivers for v7.4
Date: Tue, 13 Oct 2026 16:14:18 +0100	[thread overview]
Message-ID: <20261013-defame-busload-7eeb111f35ce@spud> (raw)

[-- Attachment #1: Type: text/plain, Size: 1217 bytes --]

Hey folks,

Might be my last mini PR here, since the RISC-V SSE driver is coming via
the actual RISC-V tree, so there'll almost certainly be a much increased
activity here going forwards.

I'm a bit late PR wise (sorry) but I blame conferences and a busy week
beforehand for that...

Thanks,
Conor.

The following changes since commit cee9395acd8043be0644b25c34bfa86623f2b935:

  Linux 7.3-rc1 (2026-08-30 13:34:40 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/conor/linux.git/ riscv-firmware-for-v7.4

for you to fetch changes up to 525e00a1bbced112f5431448842b27fa7621725f:

  firmware: microchip: use kzalloc_objs() instead of kzalloc() with multiply (2026-09-08 20:36:04 +0100)

----------------------------------------------------------------
RISC-V firmware drivers for v7.4

A single fix/cleanup for the auto update driver.

Signed-off-by: Conor Dooley <conor.dooley@microchip.com>

----------------------------------------------------------------
Hrushiraj Gandhi (1):
      firmware: microchip: use kzalloc_objs() instead of kzalloc() with multiply

 drivers/firmware/microchip/mpfs-auto-update.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

             reply	other threads:[~2026-10-13 15:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-13 15:14 Conor Dooley [this message]
2026-10-13 15:14 ` [GIT PULL][1/4] RISC-V firmware drivers for v7.4 Conor Dooley
2026-10-16 15:10 ` patchwork-bot+linux-soc
2026-10-16 17:10 ` patchwork-bot+linux-soc

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=20261013-defame-busload-7eeb111f35ce@spud \
    --to=conor@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.