Re: (subset) [PATCH v10 00/16] spi: airoha: driver fixes & improvements

[Mikhail Kshevetskiy <mikhail.kshevetskiy@iopsys.eu>]

On 10/16/25 21:49, Mark Brown wrote:
> On Sun, 12 Oct 2025 15:16:51 +0300, Mikhail Kshevetskiy wrote:
>> This patch series greatly improve airoha snfi driver and fix a
>> number of serious bugs.
>>
>> Fixed bugs:
>>  * Fix reading/writing of flashes with more than one plane per lun
>>  * Fill the buffer with 0xff before writing
>>  * Fix reading of flashes supporting continuous reading mode
>>  * Fix error paths
>>
>> [...]
> Applied to
>
>    https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
>
> Thanks!
>
> [01/16] spi: airoha: return an error for continuous mode dirmap creation cases
>         commit: 4314ffce4eb81a6c18700af1b6e29b6e0c6b9e37
> [03/16] spi: airoha: add support of dual/quad wires spi modes to exec_op() handler
>         commit: edd2e261b1babb92213089b5feadca12e3459322
> [05/16] spi: airoha: switch back to non-dma mode in the case of error
>         commit: 20d7b236b78c7ec685a22db5689b9c829975e0c3
> [06/16] spi: airoha: fix reading/writing of flashes with more than one plane per lun
>         commit: 0b7d9b25e4bc2e478c9d06281a65f930769fca09
>
> 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
>
If I do fixes or change a bit description of patches not applied to
linux-next yet, should I post a whole series or it's enough to send
patches based on linux-next?

Regards,
Mikhail Kshevetskiy