linux-kernel - Re: [PATCH] spi: spi-cadence-quadspi: Populate get

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: <159838820300.25561.6639515580662716386.b4-ty@kernel.org>
Date:   Tue, 25 Aug 2020 21:43:23 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Vignesh Raghavendra <vigneshr@...com>
Cc:     Ramuthevar Vadivel Murugan 
        <vadivel.muruganx.ramuthevar@...ux.intel.com>,
        Tudor Ambarus <tudor.ambarus@...rochip.com>,
        Boris Brezillon <boris.brezillon@...labora.com>,
        linux-kernel@...r.kernel.org, Pratyush Yadav <p.yadav@...com>,
        Jan Kiszka <jan.kiszka@...mens.com>, linux-spi@...r.kernel.org
Subject: Re: [PATCH] spi: spi-cadence-quadspi: Populate get_name() interface

On Tue, 25 Aug 2020 22:55:06 +0530, Vignesh Raghavendra wrote:
> Implement get_name() interface of spi_controller_mem_ops so as to avoid
> changing of mtd->name due to driver being moved over to spi-mem
> framework from SPI NOR. This avoids breaking of MTD cmdline args being
> passed by bootloaders which maybe using old driver name.

Applied to

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

Thanks!

[1/1] spi: spi-cadence-quadspi: Populate get_name() interface
      commit: 2ea370a9173f4a3c80b24221049359a5d1518bc0

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