mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jon Hunter <jonathanh@nvidia.com>
To: Linus Walleij <linus.walleij@linaro.org>,
	Prathamesh Shete <pshete@nvidia.com>
Cc: bgolaszewski@baylibre.com, linux-gpio@vger.kernel.org,
	linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
	thierry.reding@gmail.com, smangipudi@nvidia.com,
	Manish Bhardwaj <mbhardwaj@nvidia.com>
Subject: Re: [PATCH v2] gpio: tegra186: add Tegra234 PMC compatible in GPIO driver
Date: Mon, 9 Jan 2023 20:30:44 +0000	[thread overview]
Message-ID: <14dbbfdf-c096-439e-41c9-71e083138560@nvidia.com> (raw)
In-Reply-To: <CACRpkdbMnRNTLcCtqNjKpxWxMbAXLssnuBEuNqAfgDfj3XVfXQ@mail.gmail.com>

Hi Linus,

On 08/09/2022 14:21, Linus Walleij wrote:
> On Tue, Aug 16, 2022 at 12:27 PM Prathamesh Shete <pshete@nvidia.com> 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>
> 
> Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
> 
> It also has Thierry's ACK from v1.
> 
> Yours,
> Linus Walleij


I don't see this one in -next. Are you able to pick this up?

Reviewed-by: Jon Hunter <jonathanh@nvidia.com>
Tested-by: Jon Hunter <jonathanh@nvidia.com>

Thanks!
Jon

  reply	other threads:[~2023-01-09 20:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-24  8:24 [PATCH] " 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 [this message]
2023-01-10  8:24         ` Linus Walleij
2023-01-11  8:27           ` Bartosz Golaszewski
2022-09-15 12:38     ` Thierry Reding

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=14dbbfdf-c096-439e-41c9-71e083138560@nvidia.com \
    --to=jonathanh@nvidia.com \
    --cc=bgolaszewski@baylibre.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 \
    --cc=thierry.reding@gmail.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
Powered by JetHome