From: Dipen Patel <dipenp@nvidia.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
timestamp@lists.linux.dev, linux-tegra@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>
Subject: Re: [PATCH v1 0/4] hte: Improve GPIO handling and other cleanups
Date: Wed, 11 Oct 2023 11:04:23 -0700 [thread overview]
Message-ID: <e51793c4-e58b-8b4c-e936-2938718ee6ce@nvidia.com> (raw)
In-Reply-To: <ZSZzsfaunP5yRvZ4@smile.fi.intel.com>
On 10/11/23 3:06 AM, Andy Shevchenko wrote:
> On Wed, Oct 11, 2023 at 11:33:51AM +0200, Bartosz Golaszewski wrote:
>> On Tue, Oct 10, 2023 at 5:18 PM Andy Shevchenko
>> <andriy.shevchenko@linux.intel.com> wrote:
>>>
>>> This is a series provides a new API to GPIO library (so far only
>>> available in the GPIO tree), and respective update to the Tegra
>>> HTE driver. On top a couple of other cleaups (patches 3 & 4, they
>>> can be applied separately).
>>>
>>> Patch 2 inherited tags from its respective discussion thread [1],
>>> but I believe the Tested-by needs to be confirmed again.
>>>
>>> Due to dependencies this either should be applied to the GPIO tree,
>>> or to the HTE when GPIO updates land the upstream (optionally with
>>> the first patch be applied even now to the GPIO tree independently).
>>>
>>> Another option is to have an immutable branch or tag, but I assume
>>> that was discussed and rejected (?) in [1].
>>
>> The series looks good to me. I'd like to take patches 1 and 2 through
>> the GPIO tree once v2 is out. This way we could potentially remove
>> gpiochip_find() for v6.7 already.
>
> It would be nice to see it being removed sooner than later!
> I'm waiting for the test results by Dipen, I'll send the v2
> ASAP if tests pass.
>
Reviewed-by: Dipen Patel <dipenp@nvidia.com>
After correcting typo manually
Tested-by: Dipen Patel <dipenp@nvidia.com>
next prev parent reply other threads:[~2023-10-11 18:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 15:17 [PATCH v1 0/4] hte: Improve GPIO handling and other cleanups Andy Shevchenko
2023-10-10 15:17 ` [PATCH v1 1/4] gpiolib: provide gpio_device_find_by_fwnode() Andy Shevchenko
2023-10-13 9:21 ` Linus Walleij
2023-10-10 15:17 ` [PATCH v1 2/4] hte: tegra194: don't access struct gpio_chip Andy Shevchenko
2023-10-10 16:19 ` Dipen Patel
2023-10-10 19:31 ` Dipen Patel
2023-10-11 5:54 ` Andy Shevchenko
2023-10-11 18:05 ` Dipen Patel
2023-10-10 15:17 ` [PATCH v1 3/4] hte: tegra194: Remove redundant dev_err() Andy Shevchenko
2023-10-11 2:19 ` Dipen Patel
2023-10-10 15:17 ` [PATCH v1 4/4] hte: tegra194: Switch to LATE_SIMPLE_DEV_PM_OPS() Andy Shevchenko
2023-10-10 19:36 ` Dipen Patel
2023-10-11 5:55 ` Andy Shevchenko
2023-10-11 18:06 ` Dipen Patel
2023-10-11 9:33 ` [PATCH v1 0/4] hte: Improve GPIO handling and other cleanups Bartosz Golaszewski
2023-10-11 10:06 ` Andy Shevchenko
2023-10-11 18:04 ` Dipen Patel [this message]
2023-10-11 11:43 ` 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=e51793c4-e58b-8b4c-e936-2938718ee6ce@nvidia.com \
--to=dipenp@nvidia.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=jonathanh@nvidia.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@gmail.com \
--cc=timestamp@lists.linux.dev \
/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