From: Thierry Reding <thierry.reding@gmail.com>
To: Prathamesh Shete <pshete@nvidia.com>
Cc: linus.walleij@linaro.org, bgolaszewski@baylibre.com,
linux-gpio@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org, jonathanh@nvidia.com,
smangipudi@nvidia.com, Manish Bhardwaj <mbhardwaj@nvidia.com>
Subject: Re: [PATCH v2] gpio: tegra186: add Tegra234 PMC compatible in GPIO driver
Date: Thu, 15 Sep 2022 14:38:56 +0200 [thread overview]
Message-ID: <YyMc4OkYLLXjiHmL@orome> (raw)
In-Reply-To: <20220816102725.14708-1-pshete@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 500 bytes --]
On Tue, Aug 16, 2022 at 03:57:25PM +0530, Prathamesh Shete wrote:
> Using this patch we are adding PMC compatible string for
> Tegra234 in GPIO driver so the IRQ hierarchy can be set.
>
> Signed-off-by: Manish Bhardwaj <mbhardwaj@nvidia.com>
> Signed-off-by: Prathamesh Shete <pshete@nvidia.com>
> ---
> drivers/gpio/gpio-tegra186.c | 1 +
> 1 file changed, 1 insertion(+)
I already acked this on v1, but here goes again, for patchwork:
Acked-by: Thierry Reding <treding@nvidia.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2022-09-15 12:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 8:24 [PATCH] gpio: tegra186: add Tegra234 PMC compatible in GPIO driver Prathamesh Shete
2022-02-24 16:39 ` Thierry Reding
2022-08-16 10:27 ` [PATCH v2] " Prathamesh Shete
2022-09-08 10:31 ` Prathamesh Shete
2022-09-08 13:21 ` Linus Walleij
2023-01-09 20:30 ` Jon Hunter
2023-01-10 8:24 ` Linus Walleij
2023-01-11 8:27 ` Bartosz Golaszewski
2022-09-15 12:38 ` Thierry Reding [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=YyMc4OkYLLXjiHmL@orome \
--to=thierry.reding@gmail.com \
--cc=bgolaszewski@baylibre.com \
--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=mbhardwaj@nvidia.com \
--cc=pshete@nvidia.com \
--cc=smangipudi@nvidia.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).