linux-kernel - Re: [PATCH 2/2] spi: mediatek: move devm_spi_register

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Wed, 14 Jul 2021 16:55:14 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Mason Zhang <mason.zhang@...iatek.com>,
        Matthias Brugger <matthias.bgg@...il.com>
Cc:     Mark Brown <broonie@...nel.org>, wsd_upstream@...iatek.com,
        linux-arm-kernel@...ts.infradead.org,
        linux-mediatek@...ts.infradead.org, leilk.liu@...iatek.com,
        Mason Zhang <Mason.Zhang@...iatek.com>,
        linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] spi: mediatek: move devm_spi_register_master position

On Tue, 13 Jul 2021 19:42:48 +0800, Mason Zhang wrote:
> This patch move devm_spi_register_master to the end of mtk_spi_probe.
> If slaves call spi_sync in there probe function, master should have probe done.

Applied to

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

Thanks!

[2/2] spi: mediatek: move devm_spi_register_master position
      commit: c934fec1c32840224fd975544c347823962193b2

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