From: Peter Rosin <peda@axentia.se>
To: Bartosz Golaszewski <brgl@bgdev.pl>,
Michael Hennerich <michael.hennerich@analog.com>,
Linus Walleij <linus.walleij@linaro.org>
Cc: linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-gpio@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [PATCH] i2c: mux: ltc4306: use new GPIO line value setter callbacks
Date: Mon, 7 Apr 2025 10:08:52 +0200 [thread overview]
Message-ID: <16b14e5e-e5eb-5203-4cdf-44fbde9a5688@axentia.se> (raw)
In-Reply-To: <20250407-gpiochip-set-rv-i2c-mux-v1-1-7330a0f4df1a@linaro.org>
Hi!
2025-04-07 at 09:17, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
>
> struct gpio_chip now has callbacks for setting line values that return
> an integer, allowing to indicate failures. Convert the driver to using
> them.
>
> Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
> ---
> Peter: I know you've not been very active recently. If you prefer to
> just Ack it and let me take it through the GPIO tree, please do.
What normally happens is that I just Ack trivial things like this, and
then either Wolfram or Andi picks it. The risk of future conflicts in
this area (and cycle) should be low, so I don't think it really matters
if you pick it, but Wolfram/Andi should have first dibs, since it makes
for slightly neater PRs during the merge window.
Acked-by: Peter Rosin <peda@axentia.se>
Cheers,
Peter
next prev parent reply other threads:[~2025-04-07 8:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 7:17 [PATCH] i2c: mux: ltc4306: use new GPIO line value setter callbacks Bartosz Golaszewski
2025-04-07 8:08 ` Peter Rosin [this message]
2025-04-24 7:16 ` Bartosz Golaszewski
2025-04-24 8:10 ` Wolfram Sang
2025-04-24 8:11 ` Bartosz Golaszewski
2025-04-24 8:27 ` Wolfram Sang
2025-04-15 8:34 ` Linus Walleij
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=16b14e5e-e5eb-5203-4cdf-44fbde9a5688@axentia.se \
--to=peda@axentia.se \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.hennerich@analog.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