From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Johan Hovold <johan@kernel.org>
Cc: Bartosz Golaszewski <brgl@kernel.org>,
Andi Shyti <andi.shyti@kernel.org>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/3] i2c: dev: clean up registration
Date: Tue, 10 Nov 2026 21:06:21 +0100 [thread overview]
Message-ID: <avN5PWgseDWJJq36@shikoro> (raw)
In-Reply-To: <avMW-hz61zXUbQWV@hovoldconsulting.com>
> If Wolfram insists, I can revisit this, but I don't think it's needed.
Well, I can see both sides. One the one hand, it is a bit of an academic
excercise, on the other hand it is more "correct".
I favor the incremental approach. I won't force Johan to do something
which he thinks is superfluous. But if someone interested sends such an
incremental patch, I'd vote for inclusion. And with all the code
analysis out there, I think such a patch will come eventually.
That being said, it means I could then apply this series to my for-andi
branch and add the comment I requested here myself. But I will wait
until tomorrow to wait for further comments, if any.
next prev parent reply other threads:[~2026-11-10 20:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-27 10:20 [PATCH v2 0/3] i2c: dev: fix blocked adapter deregistration Johan Hovold
2026-08-27 10:20 ` [PATCH v2 1/3] " Johan Hovold
2026-11-09 15:08 ` Bartosz Golaszewski
2026-11-10 12:34 ` Johan Hovold
2026-08-27 10:20 ` [PATCH v2 2/3] i2c: dev: drop unnecessary sysfs device lookup Johan Hovold
2026-11-09 14:59 ` Bartosz Golaszewski
2026-11-10 11:46 ` Wolfram Sang
2026-08-27 10:20 ` [PATCH v2 3/3] i2c: dev: clean up registration Johan Hovold
2026-11-09 15:01 ` Bartosz Golaszewski
2026-11-10 11:50 ` Wolfram Sang
2026-11-10 12:42 ` Johan Hovold
2026-11-10 12:54 ` Bartosz Golaszewski
2026-11-10 13:07 ` Johan Hovold
2026-11-10 20:06 ` Wolfram Sang [this message]
2026-11-04 19:42 ` [PATCH v2 0/3] i2c: dev: fix blocked adapter deregistration Wolfram Sang
2026-11-05 8:18 ` Bartosz Golaszewski
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=avN5PWgseDWJJq36@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=andi.shyti@kernel.org \
--cc=brgl@kernel.org \
--cc=johan@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®