linux-kernel - Re: [PATCH v2 1/1] spi: Make error handling of gpiod

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: <161903040536.13608.2514437013522557183.b4-ty@kernel.org>
Date:   Wed, 21 Apr 2021 20:03:25 +0100
From:   Mark Brown <broonie@...nel.org>
To:     linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org,
        Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc:     Mark Brown <broonie@...nel.org>
Subject: Re: [PATCH v2 1/1] spi: Make error handling of gpiod_count() call cleaner

On Tue, 20 Apr 2021 19:40:40 +0300, Andy Shevchenko wrote:
> Each time we call spi_get_gpio_descs() the num_chipselect is overwritten
> either by new value or by the old one. This is an extra operation in case
> gpiod_count() returns an error. Besides that it slashes the error handling
> of gpiod_count().
> 
> Refactor the code to make error handling of gpiod_count() call cleaner.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: Make error handling of gpiod_count() call cleaner
      commit: 31ed8ebc7a27c1937184b956727bf71d4adc7df3

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