[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20260122205749.4f939243@jic23-huawei>
Date: Thu, 22 Jan 2026 20:57:49 +0000
From: Jonathan Cameron <jic23@...nel.org>
To: Andy Shevchenko <andriy.shevchenko@...el.com>
Cc: raskar.shree97@...il.com, David Lechner <dlechner@...libre.com>, Nuno
Sá <nuno.sa@...log.com>, Andy Shevchenko <andy@...nel.org>,
skhan@...uxfoundation.org, david.hunter.linux@...il.com,
linux-iio@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v6 1/5] iio: proximity: rfd77402: Reorder header
includes
On Wed, 21 Jan 2026 10:54:00 +0200
Andy Shevchenko <andriy.shevchenko@...el.com> wrote:
> On Wed, Jan 21, 2026 at 02:05:41AM +0530, Shrikant Raskar via B4 Relay wrote:
>
> > Reorder header includes to follow kernel include
> > ordering conventions.
>
> FWIW,
> Reviewed-by: Andy Shevchenko <andriy.shevchenko@...el.com>
>
Patches 1 and 2 were already queued up. I've rebuilt the merge
in my tree to drop patch 2 without breaking the rest of the history.
Shrikant, it is common for maintainer to pick up the early
part of a series whilst later parts still need more work.
If that happens, please rebase on the appropriate tree or
just drop those patches form your series that have already been
applied. Otherwise this mess happens where new review comes
in. Review is always good, but it should be clear if it
is on applied patches or not!
Jonathan
Powered by blists - more mailing lists