linux-kernel - Re: [PATCH v2] spi: spi.h: add missing kernel-doc for @last_cs_index

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: <171173373178.1605661.3810768018562164520.b4-ty@kernel.org>
Date: Fri, 29 Mar 2024 17:35:31 +0000
From: Mark Brown <broonie@...nel.org>
To: linux-kernel@...r.kernel.org, Randy Dunlap <rdunlap@...radead.org>
Cc: Andy Shevchenko <andy@...nel.org>, linux-spi@...r.kernel.org, 
 Amit Kumar Mahapatra <amit.kumar-mahapatra@....com>
Subject: Re: [PATCH v2] spi: spi.h: add missing kernel-doc for
 @last_cs_index_mask

On Thu, 28 Mar 2024 15:33:40 -0700, Randy Dunlap wrote:
> kernel-doc complains about last_cs_index_mask not described, so add its
> description.
> 
> spi.h:778: warning: Function parameter or struct member 'last_cs_index_mask' not described in 'spi_controller'
> 
> 

Applied to

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

Thanks!

[1/1] spi: spi.h: add missing kernel-doc for @last_cs_index_mask
      commit: ba5206881843e16b74a07c37970dcc44d22f8f6f

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