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 14:39:49 +0200 [thread overview]
Message-ID: <aigJlbxRhEdj1vBy@ninjato> (raw)
In-Reply-To: <aigH9xxr_2T8EZEm@zenone.zhora.eu>
[-- Attachment #1: Type: text/plain, Size: 348 bytes --]
> yes, I did spend some time looking at these patches and i was in
> doubt where to merge them. At the end I decided to split the
> series.
My suggestion: When in doubt, tend to be conservative in changing
something. Fixes can always be backported, but regression are a real
pain.
> Now they are all in the non fixes branch.
Great, thank you!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2026-06-09 12:39 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
2026-06-09 12:34 ` Andi Shyti
2026-06-09 12:39 ` Wolfram Sang [this message]
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=aigJlbxRhEdj1vBy@ninjato \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox