[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <177bcba2-2358-424a-a22c-9bd8b42cbeae@iopsys.eu>
Date: Thu, 16 Oct 2025 16:39:19 +0300
From: Mikhail Kshevetskiy <mikhail.kshevetskiy@...sys.eu>
To: Mark Brown <broonie@...nel.org>
Cc: Lorenzo Bianconi <lorenzo@...nel.org>, Ray Liu <ray.liu@...oha.com>,
Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, Matthias Brugger
<matthias.bgg@...il.com>,
AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>,
Andy Shevchenko <andy@...nel.org>, linux-arm-kernel@...ts.infradead.org,
linux-spi@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-mediatek@...ts.infradead.org,
Andreas Gnau <andreas.gnau@...sys.eu>
Subject: Re: [PATCH v10 02/16] spi: airoha: remove unnecessary restriction
length
On 10/16/25 15:04, Mark Brown wrote:
> On Sun, Oct 12, 2025 at 03:16:53PM +0300, Mikhail Kshevetskiy wrote:
>> The "length < 160" restriction is not needed because airoha_snand_write_data()
>> and airoha_snand_read_data() will properly handle data transfers above
>> SPI_MAX_TRANSFER_SIZE.
> Non-fix changes should be after fixes so there aren't any spurious
> dependencies.
Could you give me an advice?
This patch series consist of:
1) bug fixes (patches 1, 3, 5, 6, 13)
2) removing of boot related dirty hack, absolutely necessary for older
kernels (patch 12 and preparation patches 9-11)
3) improvements (patches: 2, 8)
4) cleanups (patches: 4, 7)
5) support of en7523 SoC (patches: 14-16)
What will be the best order of changes?
Regards,
Mikhail Kshevetskiy
Powered by blists - more mailing lists