public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Heiner Kallweit <hkallweit1@gmail.com>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>,
	linux-renesas-soc@vger.kernel.org, linux-i2c@vger.kernel.org
Subject: Re: [PATCH 0/2] i2c: revert flag based client handling
Date: Fri, 7 Feb 2025 14:26:02 +0100	[thread overview]
Message-ID: <1a3c4e49-695d-4882-820b-d1501a776436@gmail.com> (raw)
In-Reply-To: <Z6TqXGYIBUjhWtDH@shikoro>

On 06.02.2025 17:59, Wolfram Sang wrote:
> Hi Heiner,
> 
>> With RFC fix (v2) sent, the issue should be solved.
>> Would be good to have your feedback on the fix approach.
> 
> I had a glimpse, and the patch was too intrusive for a quick fix with
> changing the locking everywhere. So, I will still revert the original
> changes to buy us more time. In addition, as we overlooked one code
> path, we should double check that we didn't overlook another one in that
> regard, i.e. muxes. We should develop better test cases, too.
> 

Understood. How to go on from here? Bring the two patches plus v2 of the
fix to linux-next for 6.15?

I only have consumer hw w/o i2c muxes, therefore can just compile-test
the mux part.

> Happy hacking,
> 
>    Wolfram
> 
Heiner

      reply	other threads:[~2025-02-07 13:25 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 ` [PATCH 0/2] i2c: revert flag based client handling Heiner Kallweit
2025-02-06 16:59   ` Wolfram Sang
2025-02-07 13:26     ` Heiner Kallweit [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=1a3c4e49-695d-4882-820b-d1501a776436@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox