From: Heiner Kallweit <hkallweit1@gmail.com>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>,
linux-renesas-soc@vger.kernel.org
Cc: linux-i2c@vger.kernel.org
Subject: Re: [PATCH 0/2] i2c: revert flag based client handling
Date: Wed, 5 Feb 2025 15:01:09 +0100 [thread overview]
Message-ID: <87c4716f-d6bd-4a4e-91dc-70f73b9109dc@gmail.com> (raw)
In-Reply-To: <20250205134623.6921-1-wsa+renesas@sang-engineering.com>
On 05.02.2025 14:42, Wolfram Sang wrote:
> It turned out the new mechanism does not handle all muxing cases. Revert
> the changes to give a proper solution more time.
>
With RFC fix (v2) sent, the issue should be solved.
Would be good to have your feedback on the fix approach.
>
> 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(-)
>
next prev parent reply other threads:[~2025-02-05 14:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-05 13:42 [PATCH 0/2] i2c: revert flag based client handling Wolfram Sang
2025-02-05 13:42 ` [PATCH 1/2] Revert "i2c: Replace list-based mechanism for handling userspace-created clients" Wolfram Sang
2025-02-06 17:06 ` Wolfram Sang
2025-02-05 13:42 ` [PATCH 2/2] Revert "i2c: Replace list-based mechanism for handling auto-detected clients" Wolfram Sang
2025-02-06 17:06 ` Wolfram Sang
2025-02-05 14:01 ` Heiner Kallweit [this message]
2025-02-06 16:59 ` [PATCH 0/2] i2c: revert flag based client handling Wolfram Sang
2025-02-07 13:26 ` Heiner Kallweit
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=87c4716f-d6bd-4a4e-91dc-70f73b9109dc@gmail.com \
--to=hkallweit1@gmail.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=wsa+renesas@sang-engineering.com \
/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.