linux-kernel - Re: [PATCH] spi: mpc52xx-psc: Make mpc52xx_psc_spi_transfer_one

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: <169660348525.39801.7796334144610073729.b4-ty@kernel.org>
Date:   Fri, 06 Oct 2023 15:44:45 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Geert Uytterhoeven <geert+renesas@...der.be>
Cc:     linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org,
        kernel test robot <lkp@...el.com>
Subject: Re: [PATCH] spi: mpc52xx-psc: Make
 mpc52xx_psc_spi_transfer_one_message() static

On Fri, 06 Oct 2023 13:29:45 +0200, Geert Uytterhoeven wrote:
> With W=1:
> 
>     drivers/spi/spi-mpc52xx-psc.c:178:5: warning: no previous prototype for ‘mpc52xx_psc_spi_transfer_one_message’ [-Wmissing-prototypes]
>       178 | int mpc52xx_psc_spi_transfer_one_message(struct spi_controller *ctlr,
> 	  |     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 
> mpc52xx_psc_spi_transfer_one_message() is only used inside the file that
> defines it.  Hence fix this by making it static.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: mpc52xx-psc: Make mpc52xx_psc_spi_transfer_one_message() static
      commit: 881fe6ed21e8c7e60095aabc274c4f2bfdc87c5e

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