Linux GPIO subsystem development
 help / color / mirror / Atom feed
From: Dipen Patel <dipenp@nvidia.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-gpio@vger.kernel.org
Subject: Re: [PATCH v2] hte: tegra-194: Use proper includes
Date: Thu, 20 Apr 2023 14:48:31 -0700	[thread overview]
Message-ID: <2e5cfd08-f879-7ead-d2d5-dfc97907f853@nvidia.com> (raw)
In-Reply-To: <dbf568ba-22a6-3936-6acd-3a6e3260d9fa@nvidia.com>

On 4/20/23 2:22 PM, Dipen Patel wrote:
> On 1/17/23 12:41 AM, Linus Walleij wrote:
>> The test driver uses the gpiod consumer API so include the right
>> <linux/gpio/consumer.h> header. This may cause a problem with
>> struct of_device_id being implcitly pulled in by the legacy
>> header <linux/gpio.h> so include <linux/mod_devicetable.h>
>> explicitly as well.
>>
>> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> I will push this patch to HTE subsystem tree...
> 
> Acked-by: Dipen Patel <dipenp@nvidia.com>
> 
Sorry for spamming your inbox, it seems https://patchwork.kernel.org/project/linux-media/patch/20230208173343.37582-4-andriy.shevchenko@linux.intel.com/
is the latest version of the patch and its been there since Feb 2023. Do you want me to push that patch through HTE sub tree?

  reply	other threads:[~2023-04-20 21:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-17  8:41 [PATCH v2] hte: tegra-194: Use proper includes Linus Walleij
2023-04-20 20:19 ` Dipen Patel
2023-04-20 20:48   ` Linus Walleij
2023-04-20 20:54     ` Dipen Patel
2023-04-20 21:22 ` Dipen Patel
2023-04-20 21:48   ` Dipen Patel [this message]
2023-04-21  7:42     ` 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=2e5cfd08-f879-7ead-d2d5-dfc97907f853@nvidia.com \
    --to=dipenp@nvidia.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    /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