mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* linux-next: regression in i2c-imx-lpi2c.c after rust-i2c-next merge (next-20260910)
@ 2026-09-14  3:28 Carlos Song
  2026-09-14 10:17 ` Mark Brown
  0 siblings, 1 reply; 2+ messages in thread
From: Carlos Song @ 2026-09-14  3:28 UTC (permalink / raw)
  To: Mark Brown, Andi Shyti, Aisheng Dong, Frank Li, Sascha Hauer,
	Pengutronix Kernel Team, Fabio Estevam
  Cc: linux-i2c, imx, moderated list:ARM/STM32 ARCHITECTURE, LKML

Hi, Mark and Andi

While looking at next-20260910, I noticed that the merge commit:

commit 2edfbdfb8f9c5b2482232087a03fa1a6692b9e5b
Merge: 98d87b29bc8a7 61ddec70c9bcc
Author: Mark Brown <broonie@kernel.org>
Date:   Thu Sep 10 14:19:17 2026 +0100

    Merge branch 'rust-i2c-next' of https://github.com/ikrtn/rust-for-linux

    # Conflicts:
    #       drivers/i2c/busses/i2c-imx-lpi2c.c

After this merge, I meet a regression on the i.MX8Q series starting from next-20260910
(next-20260909 was still fine).

The root cause is:
Change to lpi2c_imx_probe() from this patch[1] was replaced back with the old logic during the merge conflict resolution(2edfbdfb8f9c).

Could you help pick these missing codes back?

[1] 27c9445be86b1 i2c: imx-lpi2c: avoid accessing target registers on master-only controllers

Best Regards,
Carlos


NXP Public

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2026-09-14 10:17 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2026-09-14  3:28 linux-next: regression in i2c-imx-lpi2c.c after rust-i2c-next merge (next-20260910) Carlos Song
2026-09-14 10:17 ` Mark Brown

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®