[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c4393e20-3fc8-45df-be7d-5f80dcb069bb@sirena.org.uk>
Date: Thu, 16 Oct 2025 21:07:13 +0100
From: Mark Brown <broonie@...nel.org>
To: Mikhail Kshevetskiy <mikhail.kshevetskiy@...sys.eu>
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: (subset) [PATCH v10 00/16] spi: airoha: driver fixes &
improvements
On Thu, Oct 16, 2025 at 11:01:04PM +0300, Mikhail Kshevetskiy wrote:
> On 10/16/25 21:49, Mark Brown wrote:
> > 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.
> 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?
You shouldn't resend already applied patches, base your new work on
what's already applied.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists