linux-kernel - Re: [PATCH] spi: spi-zynqmp-gqspi: fix driver kconfig dependencies

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: <169990444437.3294163.12116886943969269718.b4-ty@kernel.org>
Date:   Mon, 13 Nov 2023 19:40:44 +0000
From:   Mark Brown <broonie@...nel.org>
To:     amit.kumar-mahapatra@...inx.com, michal.simek@....com,
        Radhey Shyam Pandey <radhey.shyam.pandey@....com>
Cc:     linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org,
        git@....com, Amit Kumar Mahapatra <amit.kumar-mahapatra@....com>
Subject: Re: [PATCH] spi: spi-zynqmp-gqspi: fix driver kconfig dependencies

On Mon, 06 Nov 2023 20:23:55 +0530, Radhey Shyam Pandey wrote:
> ZynqMP GQSPI driver no longer uses spi-master framework. It had been
> converted to use spi-mem framework. So remove driver dependency from
> spi-master and replace it with spi-mem.
> 
> 

Applied to

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

Thanks!

[1/1] spi: spi-zynqmp-gqspi: fix driver kconfig dependencies
      commit: 424a8166764e462258fdccaaefbdeb07517c8b21

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