[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <vg5yex3wpnfeibgkwmi33yazdxdz2pbhn4w72mnffqm3qtvjf6@gv3syxj6gsk7>
Date: Wed, 6 Mar 2024 19:24:38 +0100
From: Uwe Kleine-König <u.kleine-koenig@...gutronix.de>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Thorsten Scherer <T.Scherer@...elmann.de>,
linux-kernel@...r.kernel.org, Pengutronix Kernel Team <kernel@...gutronix.de>,
"Ricardo B. Marliere" <ricardo@...liere.net>
Subject: siox patches for next development cycle [Re: [PATCH 0/4] siox: Move
some complexity into the core]
Hello,
On Tue, Feb 27, 2024 at 11:21:24AM +0100, Thorsten Scherer wrote:
> On Mon, Feb 19, 2024 at 08:46:28AM +0100, Uwe Kleine-König wrote:
> The series looks sensible.
>
> Acked-by: Thorsten Scherer <t.scherer@...elmann.de>
>
> @gregkh: Would you please pick up Uwe's series as well?
There are currently six patches for drivers/siox waiting to be applied.
(Two by Ricardo and four by me.) Thorsten asked Greg to do so. Greg
didn't pick these up yet though. So I collected them and put them to a
branch at:
https://git.kernel.org/pub/scm/linux/kernel/git/ukleinek/linux.git siox/for-next
I'd like to get them in during the next development cycle.
Greg, what is easiest for you? Are they still on your list of open
patches and we (I) need just a bit more patience? Or should I send a PR
to Linus when the merge window opens?
Stephen: It would be nice to get this above branch into next, no matter
if the patches make it in via Greg or me. Could you please add this
branch to your list for next? If Greg will apply them, I'll empty this
branch to not get duplicates.
Thanks to all involved people,
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | https://www.pengutronix.de/ |
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists