From: Wolfram Sang <wsa@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
Peter Rosin <peda@axentia.se>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Andi Shyti <andi.shyti@kernel.org>
Subject: [PULL REQUEST] i2c-for-6.14-rc2
Date: Sat, 8 Feb 2025 12:58:53 +0100 [thread overview]
Message-ID: <Z6dG_QT0l_ehhZd8@shikoro> (raw)
[-- Attachment #1: Type: text/plain, Size: 1096 bytes --]
The following changes since commit 2014c95afecee3e76ca4a56956a936e23283f05b:
Linux 6.14-rc1 (2025-02-02 15:39:26 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git tags/i2c-for-6.14-rc2
for you to fetch changes up to 3bfa08fe9ec8dd79e183c88e1275be74191e7bc8:
Revert "i2c: Replace list-based mechanism for handling auto-detected clients" (2025-02-05 14:22:12 +0100)
----------------------------------------------------------------
i2c-for-6.14-rc2
It turned out the new mechanism for handling created devices does not
handle all muxing cases. Revert the changes to give a proper solution
more time.
----------------------------------------------------------------
Wolfram Sang (2):
Revert "i2c: Replace list-based mechanism for handling userspace-created clients"
Revert "i2c: Replace list-based mechanism for handling auto-detected clients"
drivers/i2c/i2c-core-base.c | 113 +++++++++++++++++++++++++++++---------------
include/linux/i2c.h | 10 +++-
2 files changed, 83 insertions(+), 40 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2025-02-08 11:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-08 11:58 Wolfram Sang [this message]
2025-02-08 22:00 ` [PULL REQUEST] i2c-for-6.14-rc2 pr-tracker-bot
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=Z6dG_QT0l_ehhZd8@shikoro \
--to=wsa@kernel.org \
--cc=andi.shyti@kernel.org \
--cc=brgl@bgdev.pl \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@axentia.se \
--cc=torvalds@linux-foundation.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