linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Bartosz Golaszewski <brgl@bgdev.pl>,
	Qiang Zhao <qiang.zhao@nxp.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Magnus Damm <magnus.damm@gmail.com>
Cc: linuxppc-dev@lists.ozlabs.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
	linux-renesas-soc@vger.kernel.org,
	Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [PATCH 0/2] soc: use new GPIO line value setter callbacks
Date: Mon, 23 Jun 2025 11:54:24 +0200	[thread overview]
Message-ID: <c6eece57-8767-4435-beda-c9f399e3fa80@csgroup.eu> (raw)
In-Reply-To: <CAMRc=McVV=VBw0DRiz-4tTjh7ZtRLWg=N_LQ2-7O1sKyW30rxw@mail.gmail.com>

Hi,


Le 23/06/2025 à 09:33, Bartosz Golaszewski a écrit :
> On Tue, Jun 10, 2025 at 2:38 PM Bartosz Golaszewski <brgl@bgdev.pl> wrote:
>>
>> Commit 98ce1eb1fd87e ("gpiolib: introduce gpio_chip setters that return
>> values") added new line setter callbacks to struct gpio_chip. They allow
>> to indicate failures to callers. We're in the process of converting all
>> GPIO controllers to using them before removing the old ones. This series
>> converts all GPIO chips implemented under drivers/soc/.
>>
>> Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
>> ---
>> Bartosz Golaszewski (2):
>>        soc: fsl: qe: use new GPIO line value setter callbacks
>>        soc: renesas: pwc-rzv2m: use new GPIO line value setter callbacks
>>
>>   drivers/soc/fsl/qe/gpio.c       | 6 ++++--
>>   drivers/soc/renesas/pwc-rzv2m.c | 8 +++++---
>>   2 files changed, 9 insertions(+), 5 deletions(-)
>> ---
>> base-commit: 19272b37aa4f83ca52bdf9c16d5d81bdd1354494
>> change-id: 20250523-gpiochip-set-rv-soc-14e1d9414f70
>>
>> Best regards,
>> --
>> Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
>>
> 
> I see Geert queued patch 2/2, who would take patch 1/2?


It is in my pipe for v6.17 but if someone else wants to take it I can 
Ack it instead.

Christophe

  reply	other threads:[~2025-06-23 10:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-10 12:38 [PATCH 0/2] soc: use new GPIO line value setter callbacks Bartosz Golaszewski
2025-06-10 12:38 ` [PATCH 1/2] soc: fsl: qe: " Bartosz Golaszewski
2025-07-13  8:49   ` Bartosz Golaszewski
2025-07-30 13:34   ` Christophe Leroy
2025-06-10 12:38 ` [PATCH 2/2] soc: renesas: pwc-rzv2m: " Bartosz Golaszewski
2025-06-12 14:58   ` Geert Uytterhoeven
2025-06-23  7:33 ` [PATCH 0/2] soc: " Bartosz Golaszewski
2025-06-23  9:54   ` Christophe Leroy [this message]
2025-06-23  9:55     ` Bartosz Golaszewski
2025-06-23 10:05       ` Christophe Leroy
2025-07-07  8:40         ` Bartosz Golaszewski

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=c6eece57-8767-4435-beda-c9f399e3fa80@csgroup.eu \
    --to=christophe.leroy@csgroup.eu \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=brgl@bgdev.pl \
    --cc=geert+renesas@glider.be \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=magnus.damm@gmail.com \
    --cc=qiang.zhao@nxp.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;
as well as URLs for NNTP newsgroup(s).