From: Thierry Reding <thierry.reding@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>
Cc: Jonathan Hunter <jonathanh@nvidia.com>,
linux-gpio@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: [PATCH 1/2] dt-bindings: gpio: Use Tegra186-specific include guard
Date: Fri, 27 Nov 2020 15:08:51 +0100 [thread overview]
Message-ID: <20201127140852.123192-2-thierry.reding@gmail.com> (raw)
In-Reply-To: <20201127140852.123192-1-thierry.reding@gmail.com>
From: Thierry Reding <treding@nvidia.com>
Use a unique include guard for the Tegra186 GPIO DT bindings header to
avoid clashes with the DT bindings header for earlier chips.
Signed-off-by: Thierry Reding <treding@nvidia.com>
---
include/dt-bindings/gpio/tegra186-gpio.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/dt-bindings/gpio/tegra186-gpio.h b/include/dt-bindings/gpio/tegra186-gpio.h
index 0782b05e2775..af0d9583be70 100644
--- a/include/dt-bindings/gpio/tegra186-gpio.h
+++ b/include/dt-bindings/gpio/tegra186-gpio.h
@@ -8,8 +8,8 @@
* The second cell contains standard flag values specified in gpio.h.
*/
-#ifndef _DT_BINDINGS_GPIO_TEGRA_GPIO_H
-#define _DT_BINDINGS_GPIO_TEGRA_GPIO_H
+#ifndef _DT_BINDINGS_GPIO_TEGRA186_GPIO_H
+#define _DT_BINDINGS_GPIO_TEGRA186_GPIO_H
#include <dt-bindings/gpio/gpio.h>
--
2.29.2
next prev parent reply other threads:[~2020-11-27 14:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-27 14:08 [PATCH 0/2] gpio: tegra: Convert to gpio_irq_chip Thierry Reding
2020-11-27 14:08 ` Thierry Reding [this message]
2020-12-05 21:35 ` [PATCH 1/2] dt-bindings: gpio: Use Tegra186-specific include guard Linus Walleij
2020-11-27 14:08 ` [PATCH 2/2] gpio: tegra: Convert to gpio_irq_chip Thierry Reding
2020-12-01 15:08 ` Bartosz Golaszewski
2020-12-05 21:33 ` Linus Walleij
2020-12-18 14:49 ` Thierry Reding
2021-01-06 10:59 ` Bartosz Golaszewski
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=20201127140852.123192-2-thierry.reding@gmail.com \
--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-tegra@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