linux-kernel - Re: [PATCH] spi: amlogic: fix spifc build error

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] [day] [month] [year] [list]

Message-Id: <176055364173.227902.13691115706455809982.b4-ty@kernel.org>
Date: Wed, 15 Oct 2025 19:40:41 +0100
From: Mark Brown <broonie@...nel.org>
To: Liang Yang <liang.yang@...ogic.com>, Feng Chen <feng.chen@...ogic.com>, 
 Xianwei Zhao <xianwei.zhao@...ogic.com>
Cc: linux-amlogic@...ts.infradead.org, linux-spi@...r.kernel.org, 
 linux-kernel@...r.kernel.org, Guenter Roeck <linux@...ck-us.net>
Subject: Re: [PATCH] spi: amlogic: fix spifc build error

On Wed, 15 Oct 2025 15:36:59 +0800, Xianwei Zhao wrote:
> There is an error building when
> Compiler version: gcc (GCC) 14.3.0
> Assembler version: GNU assembler (GNU Binutils) 2.44
> "
>  Error log:
>  WARNING: modpost: missing MODULE_DESCRIPTION() in arch/arm/probes/kprobes/test-kprobes.o
>  ERROR: modpost: "__ffsdi2" [drivers/spi/spi-amlogic-spifc-a4.ko] undefined!
> "
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: amlogic: fix spifc build error
      commit: 6b6e03106163458716c47df2baa9ad08ed4ddb0e

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