[PATCH v3 0/4] fix the SpacemiT P1 Kconfig and resend the K1 I2C ILCR patch.
Troy Mitchell
troy.mitchell at linux.spacemit.com
Mon Dec 22 01:36:00 PST 2025
On Fri, Dec 19, 2025 at 11:26:34AM +0000, Lee Jones wrote:
> Hi Konstantin,
>
> > This series was applied to riscv/linux.git (fixes)
> > by Alexandre Belloni <alexandre.belloni at bootlin.com>:
> >
> > On Tue, 18 Nov 2025 14:08:04 +0800 you wrote:
> > > Since P1 Kconfig directly selects K1_I2C, after the I2C ILCR patch was
> > > merged, the driver would fail [1] when COMMON_CLK was not selected.
> > >
> > > This series fixes the P1 Kconfig and resends the I2C ILCR patch(This
> > > patch has reverted by maintainer [2]).
> > >
> > > Now, P1 Kconfig patch has been merged[3], so I2C ILCR patch can be
> > > merged as well.
> > >
> > > [...]
> >
> > Here is the summary with links:
> > - [v3,1/4] i2c: spacemit: configure ILCR for accurate SCL frequency
> > (no matching commit)
> > - [v3,2/4] rtc: spacemit: MFD_SPACEMIT_P1 as dependencies
> > https://git.kernel.org/riscv/c/16bd954c9336
> > - [v3,3/4] regulator: spacemit: MFD_SPACEMIT_P1 as dependencies
> > (no matching commit)
>
> > - [v3,4/4] mfd: simple-mfd-i2c: add default value
> > (no matching commit)
>
> I was just about to send another snot-o-gram about people picking up
> patches without the correct Acks, but I just realised this is the same
> Patchwork issue we spoke about a couple of weeks ago.
>
> This formatting is very confusing, since at first blush it looks as
> though the whole patch-set was applied.
>
> Please can we only list patches that were merged?
I agree. At first glance, I also thought the entire series was applied.
- Troy
>
> --
> Lee Jones [李琼斯]
>
More information about the linux-riscv
mailing list