linux-kernel - Re: [PATCH 1/2] rust: macros: allow optional trailing comma in module!

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <175008906033.262451.8015418058709433630.b4-ty@kernel.org>
Date: Mon, 16 Jun 2025 16:51:00 +0100
From: Mark Brown <broonie@...nel.org>
To: rust-for-linux@...r.kernel.org, Eunsoo Eun <ewhk9887@...il.com>
Cc: linux-kernel@...r.kernel.org, Eunsoo Eun <naturale@...s.ac.kr>, 
 Benno Lossin <lossin@...nel.org>
Subject: Re: [PATCH 1/2] rust: macros: allow optional trailing comma in
 module!

On Sat, 14 Jun 2025 17:13:09 +0900, Eunsoo Eun wrote:
> Make the `module!` macro syntax more flexible by allowing an optional
> trailing comma after the last field. This makes it consistent with
> Rust’s general syntax patterns where trailing commas are allowed in
> structs, arrays, and other comma-separated lists.
> 
> For example, these are now all valid:
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next

Thanks!

[1/2] rust: macros: allow optional trailing comma in module!
      (no commit info)
[1/2] spi: spi-pci1xxxx: Drop MSI-X usage as unsupported by DMA engine
      commit: 9f0ad43b158d07bc7144d219ceabdea36e28e392

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark