Re: [GIT PULL] rust-i2c-next for 7.3
Andi Shyti <[email protected]>
| Newsgroups | org.kernel.vger.rust-for-linux,org.kernel.vger.linux-i2c,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <[email protected]> |
Hi Geert, On Mon, Aug 24, 2026 at 09:54:09AM +0200, Geert Uytterhoeven wrote: > On Mon, 24 Aug 2026 at 01:30, Andi Shyti <[email protected]> wrote: > > > No problem, rebased on i2c/i2c. Updated pull below. > > > > Thank you! > > > > > Thanks > > > Igor > > > > > > The following changes since commit 7a79b02dd1b09c235c3cf6075bccca2160d1b826: > > > > > > i2c: rcar: fix reset handling for Gen5 (2026-08-19 22:07:13 +0200) > > > > > > are available in the Git repository at: > > > > > > https://github.com/ikrtn/linux.git tags/rust-i2c-for-7.3 > > > > > > for you to fetch changes up to b5fa55ad007059547c9139d4c4872e158ae255f2: > > > > > > i2c: rust: mark I2cAdapter methods as inline (2026-08-22 12:22:27 +0100) > > > > merged to i2c/i2c. > > Apparently you merged both branches, now having the same commit twice: > > + 61ddec70c9bcc3d4 i2c: rust: mark I2cAdapter methods as inline > + b5fa55ad00705954 i2c: rust: mark I2cAdapter methods as inline > > Gr{oetje,eeting}s, Thanks for checking and letting me know! It's in i2c/i2c-next (or next/master). I made the mistake of not cleaning up the first merge before pushing the change. Since this duplicate merge log will never reach mainline, I don't want to rewrite the i2c-next branch history now. Everything will be reset to mainline at 7.3-rc1 anyway. Andi