Hi Wolfram,
at this stage, four fixes make up a fat pull request, but there
has been some turmoil in the last week. The rush to get things
sent by the merge window might have generated the need for some
fixes.
One patch was removed from the pull request because it broke the
Exynos5 I2C on all platforms. For this, I really need to thank
Marek for the prompt report.
Thanks,
Andi
The following changes since commit cf8281b1aeab93a03c87033a741075c39ace80d4:
i2c: imx: when being a target, mark the last read as processed (2024-02-22 09:02:16 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/andi.shyti/linux.git tags/i2c-host-fixes-6.8
for you to fetch changes up to 1f78f0901011c56801ff957f59152f390e8574b9:
i2c: aspeed: Fix the dummy irq expected print (2024-03-07 20:54:00 +0100)
----------------------------------------------------------------
Two patches from Heiner for the i801 are targeting muxes
discovered while working on some other features. Essentially,
there is a reordering when adding optional slaves and proper
cleanup upon registering a mux device.
Christophe fixes the exit path in the wmt driver that was leaving
the clocks hanging, and the last fix from Tommy avoids false
error reports in IRQ.
----------------------------------------------------------------
Christophe JAILLET (1):
i2c: wmt: Fix an error handling path in wmt_i2c_probe()
Heiner Kallweit (2):
i2c: i801: Fix using mux_pdev before it's set
i2c: i801: Avoid potential double call to gpiod_remove_lookup_table
Tommy Huang (1):
i2c: aspeed: Fix the dummy irq expected print
drivers/i2c/busses/i2c-aspeed.c | 1 +
drivers/i2c/busses/i2c-i801.c | 6 ++++--
drivers/i2c/busses/i2c-wmt.c | 6 +++++-
3 files changed, 10 insertions(+), 3 deletions(-)
Hi Andi,
thanks, pulled!
> at this stage, four fixes make up a fat pull request, but there
> has been some turmoil in the last week. The rush to get things
> sent by the merge window might have generated the need for some
> fixes.
Don't worry, it is a bit more than usual but not really "fat" in my
book. One wish, though: If your fixes branches are upstream, could you
rebase the fixes branch to the latest rc? So, that only the unapplied
patches are in there?
Thanks,
Wolfram
Hi Wolfram,
> thanks, pulled!
thank you!
> > at this stage, four fixes make up a fat pull request, but there
> > has been some turmoil in the last week. The rush to get things
> > sent by the merge window might have generated the need for some
> > fixes.
>
> Don't worry, it is a bit more than usual but not really "fat" in my
> book. One wish, though: If your fixes branches are upstream, could you
> rebase the fixes branch to the latest rc? So, that only the unapplied
> patches are in there?
Sure, will do. From the next cycle I will keep everything rebased
on top of the latest RC.
Thank you,
Andi