linux-kernel - Re: [PATCH 1/3] spi: sprd: Pass offset instead of physical address to adi_read/

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: <162988541636.8193.7086076559922137758.b4-ty@kernel.org>
Date:   Wed, 25 Aug 2021 11:22:37 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Chunyan Zhang <zhang.lyra@...il.com>
Cc:     Mark Brown <broonie@...nel.org>,
        LKML <linux-kernel@...r.kernel.org>,
        Baolin Wang <baolin.wang7@...il.com>,
        linux-spi@...r.kernel.org, Orson Zhai <orsonzhai@...il.com>,
        Chunyan Zhang <chunyan.zhang@...soc.com>,
        Luting Guo <luting.guo@...soc.com>
Subject: Re: [PATCH 1/3] spi: sprd: Pass offset instead of physical address to adi_read/_write()

On Tue, 24 Aug 2021 15:02:10 +0800, Chunyan Zhang wrote:
> From: Chunyan Zhang <chunyan.zhang@...soc.com>
> 
> The register offset would be added a physical address base and then pass to
> the function sprd_adt_read()/_write() each time before calling them. So we
> can do that within these two functions instead, that would make the code
> more clear.
> 
> [...]

Applied to

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

Thanks!

[1/3] spi: sprd: Pass offset instead of physical address to adi_read/_write()
      commit: 5dc349ec131c6d40aeb2545064e285f0025fbb39
[2/3] spi: sprd: Make sure offset not equal to slave address size
      commit: 2b961c51f4d35c45116b21936b563cbb78fba540
[3/3] spi: sprd: fill offset only to RD_CMD register for reading from slave device
      commit: f674aacd5005184acf3cf7b851a299573d64fdd6

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