From: Bjorn Helgaas <helgaas@kernel.org>
To: Johan Hovold <johan@kernel.org>
Cc: Bartosz Golaszewski <brgl@kernel.org>,
Manivannan Sadhasivam <mani@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI/pwrctrl: tc9563: take i2c adapter module reference
Date: Mon, 20 Jul 2026 06:04:17 -0500 [thread overview]
Message-ID: <20260720110417.GA321880@bhelgaas> (raw)
In-Reply-To: <al30lyKsG3ywkiJu@hovoldconsulting.com>
On Mon, Jul 20, 2026 at 12:12:39PM +0200, Johan Hovold wrote:
> On Fri, Jul 17, 2026 at 11:58:41AM -0500, Bjorn Helgaas wrote:
> > On Thu, Jul 16, 2026 at 03:25:32PM +0200, Johan Hovold wrote:
> > > The i2c subsystem currently blocks during adapter deregistration
> > > whenever there are consumers holding a reference.
> > >
> > > Switch to using of_get_i2c_adapter_by_node() which also takes a
> > > reference to the adapter module so that an attempt to unload the module
> > > while in use fails gracefully instead of blocking uninterruptibly.
> > >
> > > Signed-off-by: Johan Hovold <johan@kernel.org>
> >
> > Applied to pci/pwrctrl for v7.3, thanks!
> >
> > Gemini suggested minor commit log rewording, let me know if it makes it
> > worse. I do like the impact being mentioned in the subject:
> >
> > PCI/pwrctrl: tc9563: Avoid uninterruptible hang on in-use I2C module unload
> >
> > The I2C subsystem blocks during adapter deregistration if there are
> > consumers actively holding a reference.
> >
> > Switch to of_get_i2c_adapter_by_node(), which also takes a reference to the
> > adapter module, so an attempt to unload the module while in use will fail
> > gracefully instead of blocking uninterruptibly.
>
> No, please don't rewrite my commit messages (and especially not without
> clearly documenting that you've done).
>
> If you have any concerns about the wording, I can try to accommodate
> those in a v2.
>
> If I had considered this to be a fix (the line is admittedly blurry) I
> would also have tried to be more explicit about the impact in the
> summary. But here I think the existing summary is sufficient.
>
> Note that I've sent similar changes for other subsystems and there is
> some value in using the same patch summary (modulo subsystem preferences
> for capitalisation, etc).
You're right, I'm sorry. I used your original commit message. I
assumed this was for v7.3, but let me know if it should be for v7.2.
next prev parent reply other threads:[~2026-07-20 11:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 13:25 [PATCH] PCI/pwrctrl: tc9563: take i2c adapter module reference Johan Hovold
2026-07-16 13:41 ` sashiko-bot
2026-07-16 16:47 ` Manivannan Sadhasivam
2026-07-17 8:59 ` Bartosz Golaszewski
2026-07-17 16:58 ` Bjorn Helgaas
2026-07-20 10:12 ` Johan Hovold
2026-07-20 11:04 ` Bjorn Helgaas [this message]
2026-07-20 12:05 ` Johan Hovold
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=20260720110417.GA321880@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=brgl@kernel.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mani@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox