All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Markus Stockhausen <markus.stockhausen@gmx.de>
Cc: andi.shyti@kernel.org, linusw@kernel.org, brgl@kernel.org,
	linux-i2c@vger.kernel.org, linux-gpio@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Sander Vanheule <sander@svanheule.net>,
	Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
Subject: Re: [PATCH v5] i2c: i2c-gpio: Enhance driver for buses with shared SCL
Date: Mon, 13 Jul 2026 15:13:38 +0200	[thread overview]
Message-ID: <alTkghp_ejexF9ss@shikoro> (raw)
In-Reply-To: <20260713062021.2995641-1-markus.stockhausen@gmx.de>

[-- Attachment #1: Type: text/plain, Size: 546 bytes --]

Hi Markus,

>   - Send to LKML for Sashiko review

So, the review is here[1] now and it is fortunately not complaining
much. About the first issue ('bit_test'), I could imagine we add another
bool to 'struct i2c_algo_bit_data' like 'disallow_bit_test' and bail out
early if it is set? I didn't dive into the second issue ('ENOENT')
because I guess this is just a little extra handling. And you are more
into the details anyhow.

Happy hacking,

   Wolfram

[1] https://sashiko.dev/#/patchset/20260713062021.2995641-1-markus.stockhausen%40gmx.de


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2026-07-13 13:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-13  6:20 [PATCH v5] i2c: i2c-gpio: Enhance driver for buses with shared SCL Markus Stockhausen
2026-07-13 13:13 ` 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=alTkghp_ejexF9ss@shikoro \
    --to=wsa+renesas@sang-engineering.com \
    --cc=andi.shyti@kernel.org \
    --cc=bartosz.golaszewski@oss.qualcomm.com \
    --cc=brgl@kernel.org \
    --cc=linusw@kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markus.stockhausen@gmx.de \
    --cc=sander@svanheule.net \
    /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.