linux-kernel - Re: [PATCH] spi: sun4i: add support for GPIO chip select lines

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: <174464072481.99542.17446384569030524351.b4-ty@kernel.org>
Date: Mon, 14 Apr 2025 15:25:24 +0100
From: Mark Brown <broonie@...nel.org>
To: Chen-Yu Tsai <wens@...e.org>, Jernej Skrabec <jernej.skrabec@...il.com>, 
 Samuel Holland <samuel@...lland.org>, Mans Rullgard <mans@...sr.com>
Cc: Pan Nan <pannan@...winnertech.com>, Maxime Ripard <mripard@...nel.org>, 
 linux-spi@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, 
 linux-sunxi@...ts.linux.dev, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] spi: sun4i: add support for GPIO chip select lines

On Thu, 10 Apr 2025 12:53:03 +0100, Mans Rullgard wrote:
> Set use_gpio_descriptors to true so that GPIOs can be used for chip
> select in accordance with the DT binding.
> 
> 

Applied to

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

Thanks!

[1/1] spi: sun4i: add support for GPIO chip select lines
      commit: 36ff6c3f5084f2dbb6cd89d15b78cf734e9abfa6

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