From: Hans Verkuil <hverkuil@xs4all.nl>
To: Linus Walleij <linus.walleij@linaro.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
Andrzej Hajda <andrzej.hajda@intel.com>,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org
Subject: Re: [PATCH 4/4] media: i2c: s5c73m3: switch to using gpiod API
Date: Sat, 26 Nov 2022 11:39:52 +0100 [thread overview]
Message-ID: <e583b75d-feeb-bb33-1567-e7dde4f04ed7@xs4all.nl> (raw)
In-Reply-To: <e4609919-d9be-33c4-1488-352443523b14@xs4all.nl>
On 26/11/2022 11:34, Hans Verkuil wrote:
> Hi Linus,
>
> On 17/11/2022 10:06, Linus Walleij wrote:
>> On Tue, Nov 15, 2022 at 11:11 PM Dmitry Torokhov
>> <dmitry.torokhov@gmail.com> wrote:
>>
>>> This patch switches the driver away from legacy gpio/of_gpio API to
>>> gpiod API, and removes use of of_get_named_gpio_flags() which I want to
>>> make private to gpiolib.
>>>
>>> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
>>
>> Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
>
> There are now two patches that do this switch to using the gpiod API:
> this one, and one from you:
>
> https://patchwork.linuxtv.org/project/linux-media/patch/20221108100604.1500909-1-linus.walleij@linaro.org/
And a third one as well:
https://patchwork.linuxtv.org/project/linux-media/patch/20221116194307.164543-1-mairacanal@riseup.net/
>
> Any preference?
>
> Regards,
>
> Hans
next prev parent reply other threads:[~2022-11-26 10:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 22:11 [PATCH 1/4] media: i2c: s5k6a3: " Dmitry Torokhov
2022-11-15 22:11 ` [PATCH 2/4] media: i2c: s5k5baf: " Dmitry Torokhov
2022-11-17 10:54 ` Tommaso Merciai
2022-11-15 22:11 ` [PATCH 3/4] media: i2c: s5c73m3: remove support for platform data Dmitry Torokhov
2022-11-17 11:05 ` Tommaso Merciai
2022-11-28 8:39 ` Hans Verkuil
2022-11-28 19:50 ` Dmitry Torokhov
2022-11-15 22:11 ` [PATCH 4/4] media: i2c: s5c73m3: switch to using gpiod API Dmitry Torokhov
2022-11-17 9:06 ` Linus Walleij
2022-11-26 10:34 ` Hans Verkuil
2022-11-26 10:39 ` Hans Verkuil [this message]
2022-11-26 21:49 ` Linus Walleij
2022-11-17 11:06 ` Tommaso Merciai
2022-11-17 9:04 ` [PATCH 1/4] media: i2c: s5k6a3: " Linus Walleij
2022-11-17 9:11 ` Tommaso Merciai
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=e583b75d-feeb-bb33-1567-e7dde4f04ed7@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=andrzej.hajda@intel.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=s.nawrocki@samsung.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
all inboxes | Powered by JetHome®