linux-kernel - Re: [PATCH v6 1/3] spi: uapi: unify SPI modes into a single spi.h header

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]

Date:   Mon, 28 Dec 2020 16:14:28 +0000
From:   Mark Brown <broonie@...nel.org>
To:     linux-spi@...r.kernel.org,
        Alexandru Ardelean <alexandru.ardelean@...log.com>,
        linux-kernel@...r.kernel.org, devicetree@...r.kernel.org
Cc:     robh+dt@...nel.org, dragos.bogdan@...log.com,
        andy.shevchenko@...il.com
Subject: Re: [PATCH v6 1/3] spi: uapi: unify SPI modes into a single spi.h header

On Mon, 21 Dec 2020 17:29:34 +0200, Alexandru Ardelean wrote:
> This change moves all the SPI mode bits into a separate 'spi.h' header in
> uAPI. This is meant to re-use these definitions inside the kernel as well
> as export them to userspace (via uAPI).
> 
> The SPI mode definitions have usually been duplicated between between
> 'include/linux/spi/spi.h' and 'include/uapi/linux/spi/spidev.h', so
> whenever adding a new entry, this would need to be put in both headers.
> 
> [...]

Applied to

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

Thanks!

[1/3] spi: uapi: unify SPI modes into a single spi.h header
      commit: f7005142dacea1769fba0152c493aaa61b33205c
[2/3] spi: Add SPI_NO_TX/RX support
      commit: d962608ce2188a1d46ec9d356d6fad5cd6fc0341
[3/3] spi: dt-bindings: document zero value for spi-{rx,tx}-bus-width properties
      commit: ffe9819b6766b9a623822f3427df4953ab448127

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