linux-kernel - Re: (subset) [PATCH v2 0/9] Add QPIC SPI NAND support for IPQ5424 and IPQ5332 platforms

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: <176052182781.20973.15827273241958819780.b4-ty@kernel.org>
Date: Wed, 15 Oct 2025 10:50:27 +0100
From: Mark Brown <broonie@...nel.org>
To: robh@...nel.org, krzk+dt@...nel.org, conor+dt@...nel.org, 
 andersson@...nel.org, konradybcio@...nel.org, vkoul@...nel.org, 
 linux-arm-msm@...r.kernel.org, linux-spi@...r.kernel.org, 
 devicetree@...r.kernel.org, linux-kernel@...r.kernel.org, 
 dmaengine@...r.kernel.org, Md Sadre Alam <quic_mdalam@...cinc.com>
Cc: quic_varada@...cinc.com
Subject: Re: (subset) [PATCH v2 0/9] Add QPIC SPI NAND support for IPQ5424
 and IPQ5332 platforms

On Wed, 08 Oct 2025 14:34:04 +0530, Md Sadre Alam wrote:
> v2:
>  * Added Reviewed-by tag
>  * Added Acked-by tag
>  * Updated board name in commit message header
>  * Added \n before status
> 
> v1:
>  * Added support for spi nand for IPQ5424 and IPQ5332
>  * Updated bam_prep_ce_le32() to set the mask field conditionally based
>    on command
>  * Removed eMMC node for IPQ5424 and IPQ5332
> 
> [...]

Applied to

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

Thanks!

[1/9] spi: dt-bindings: spi-qpic-snand: Add IPQ5424 compatible
      commit: 454cd43a283f7697297c52981c7a499a16725656
[2/9] spi: dt-bindings: spi-qpic-snand: Add IPQ5332 compatible
      commit: 4412ab501677606436e5c49e41151a1e6eac7ac0

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