linux-kernel - Re: [PATCH 0/5] spi: spi-zynqmp-gqspi: fix spi issues

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <161858883110.29027.5432599534762847384.b4-ty@kernel.org>
Date:   Fri, 16 Apr 2021 17:01:46 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Amit Kumar Mahapatra <amit.kumar-mahapatra@...inx.com>,
        quanyang.wang@...driver.com, Michal Simek <michal.simek@...inx.com>
Cc:     Mark Brown <broonie@...nel.org>, linux-kernel@...r.kernel.org,
        linux-arm-kernel@...ts.infradead.org, linux-spi@...r.kernel.org
Subject: Re: [PATCH 0/5] spi: spi-zynqmp-gqspi: fix spi issues

On Fri, 16 Apr 2021 22:20:42 +0800, quanyang.wang@...driver.com wrote:
> V2:
> Remove all "Fixes:" tags since they base on some patches are not
> with "Fixes:".
> 
> V1:
> This series fix some issues that occurs in spi-zynqmp-gqspi.c.
> 
> [...]

Applied to

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

Thanks!

[1/5] spi: spi-zynqmp-gqspi: fix clk_enable/disable imbalance issue
      commit: c6bdae08012b2ca3e94f3a41ef4ca8cfe7c9ab6f
[2/5] spi: spi-zynqmp-gqspi: fix hang issue when suspend/resume
      commit: 799f923f0a66a9c99f0a3eaa078b306db7a8b33a
[3/5] spi: spi-zynqmp-gqspi: Resolved slab-out-of-bounds bug
      commit: 2530b3df4326023a171977ab46fdfeac0340f5b2
[4/5] spi: spi-zynqmp-gqspi: fix use-after-free in zynqmp_qspi_exec_op
      commit: a2c5bedb2d55dd27c642c7b9fb6886d7ad7bdb58
[5/5] spi: spi-zynqmp-gqspi: return -ENOMEM if dma_map_single fails
      commit: 126bdb606fd2802454e6048caef1be3e25dd121e

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