From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Andi Shyti <andi.shyti@kernel.org>
Cc: linux-i2c@vger.kernel.org, Johan Hovold <johan@kernel.org>
Subject: Re: [PULL REQUEST] i2c/fix-registration for v7.2
Date: Tue, 9 Jun 2026 13:07:19 +0200 [thread overview]
Message-ID: <aifz56BVLCdk-lDu@shikoro> (raw)
In-Reply-To: <aifphmi1oFYZz7dQ@zenone.zhora.eu>
[-- Attachment #1: Type: text/plain, Size: 1078 bytes --]
Hi Andi,
> > Johan Hovold (10):
> > i2c: core: fix irq domain leak on adapter registration failure
> > i2c: core: fix hang on adapter registration failure
> > i2c: core: fix NULL-deref on adapter registration failure
> > i2c: core: fix adapter probe deferral loop
> > i2c: core: fix adapter debugfs creation
> > i2c: core: disable runtime PM on adapter registration failure
> > i2c: core: fix adapter registration race
> > i2c: core: fix adapter deregistration race
>
> I cherry-picked until here in i2c-host-fixes.
Please don't use 'fixes'. These changes are too intrusive to be added so
late in the cycle. Stable maintainers can decide if they want to
backport this. While -next gets some testing, a lot more testing is done
once it hits Linus' tree. If we cause a regression now, we won't have
another rc to fix it. If a regression shows up during the mergewindow,
we have multiple options to deal with it (fix it, revert it). Next
mergewindow is totally fine for this.
All the best,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-06-09 11:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-08 20:27 [PULL REQUEST] i2c/fix-registration for v7.2 Wolfram Sang
2026-06-09 10:25 ` Andi Shyti
2026-06-09 11:07 ` Wolfram Sang [this message]
2026-06-09 12:34 ` Andi Shyti
2026-06-09 12:39 ` Wolfram Sang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aifz56BVLCdk-lDu@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=andi.shyti@kernel.org \
--cc=johan@kernel.org \
--cc=linux-i2c@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.