[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <10f00229-4cc0-4511-a39e-14e2c58ba98a@linux.intel.com>
Date: Fri, 5 Jan 2024 11:54:52 +0200
From: Jarkko Nikula <jarkko.nikula@...ux.intel.com>
To: Wolfram Sang <wsa@...nel.org>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Mario Limonciello <mario.limonciello@....com>,
Herbert Xu <herbert@...dor.apana.org.au>, Andi Shyti
<andi.shyti@...nel.org>, linux-i2c@...r.kernel.org,
linux-kernel@...r.kernel.org,
Mika Westerberg <mika.westerberg@...ux.intel.com>,
Jan Dabros <jsd@...ihalf.com>, Philipp Zabel <p.zabel@...gutronix.de>
Subject: Re: [PATCH v5 00/24] i2c: designware: code consolidation & cleanups
Hi Wolfram
On 12/19/23 12:23, Wolfram Sang wrote:
>
>> Wolfram, is there any chance to get this into this (v6.8) cycle?
>
> Sure, due to lots of travels and other issues I am in general very late
> with preparing the merge window.
>
> Applied to for-next, thanks!
>
Can we put this on hold from not being queued into v6.8 or better drop
the whole patchset?
Andy is right now out of office and there is a serious i2c-designware
regression in linux-next on AMD machine and I'm not able to figure out
quickly reason for it:
https://lore.kernel.org/linux-i2c/20231229120820.GCZY62tM7z4v2XmOAZ@fat_crate.local/
Powered by blists - more mailing lists