linux-kernel - Re: [PATCH v1 1/1] spi: pxa2xx: Remove redundant ->read() and ->write() in struct chip

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: <163768666834.1388476.6693782453089642459.b4-ty@kernel.org>
Date:   Tue, 23 Nov 2021 16:57:48 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
        linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org,
        linux-arm-kernel@...ts.infradead.org
Cc:     Robert Jarzmik <robert.jarzmik@...e.fr>,
        Daniel Mack <daniel@...que.org>,
        Haojian Zhuang <haojian.zhuang@...il.com>
Subject: Re: [PATCH v1 1/1] spi: pxa2xx: Remove redundant ->read() and ->write() in struct chip_data

On Mon, 22 Nov 2021 22:06:22 +0200, Andy Shevchenko wrote:
> Since the commit 196b0e2cf237 ("spi: pxa2xx: Remove if statement
> that is always true in pump_transfers()") the ->read() and ->write()
> methods in the struct driver_data are reconfigured for each transfer.
> Hence no need to keep the intermediate state in the struct chip_data.
> 
> The same applies to n_bytes member of the same data structure.
> Get rid of unneeded storage for good.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: pxa2xx: Remove redundant ->read() and ->write() in struct chip_data
      commit: 44ec41b7f7831f91c79a06de5e45f2d7ce6e4fbd

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