From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Linus Walleij <linusw@kernel.org>, Bartosz Golaszewski <brgl@kernel.org>
Subject: [PATCH v1 1/1] gpiolib: Put stubs in order in linux/gpio/driver.h
Date: Wed, 21 Oct 2026 16:55:43 +0200 [thread overview]
Message-ID: <20261021145543.567959-1-andriy.shevchenko@linux.intel.com> (raw)
The stubs in linux/gpio/driver.h go in a slightly different order
than declarations. Put stubs in the same order.
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
---
include/linux/gpio/driver.h | 24 +++++++++++-------------
1 file changed, 11 insertions(+), 13 deletions(-)
diff --git a/include/linux/gpio/driver.h b/include/linux/gpio/driver.h
index 7918b1575201..f3f913691a59 100644
--- a/include/linux/gpio/driver.h
+++ b/include/linux/gpio/driver.h
@@ -837,6 +837,17 @@ struct gpio_device *gpio_device_find_by_fwnode(const struct fwnode_handle *fwnod
#include <asm/bug.h>
+static inline int gpiochip_lock_as_irq(struct gpio_chip *gc, unsigned int offset)
+{
+ WARN_ON(1);
+ return -EINVAL;
+}
+
+static inline void gpiochip_unlock_as_irq(struct gpio_chip *gc, unsigned int offset)
+{
+ WARN_ON(1);
+}
+
static inline struct gpio_chip *gpiod_to_chip(const struct gpio_desc *desc)
{
/* GPIO can never have been requested */
@@ -873,19 +884,6 @@ static inline struct gpio_device *gpio_device_find_by_fwnode(const struct fwnode
WARN_ON(1);
return NULL;
}
-
-static inline int gpiochip_lock_as_irq(struct gpio_chip *gc,
- unsigned int offset)
-{
- WARN_ON(1);
- return -EINVAL;
-}
-
-static inline void gpiochip_unlock_as_irq(struct gpio_chip *gc,
- unsigned int offset)
-{
- WARN_ON(1);
-}
#endif /* CONFIG_GPIOLIB */
static inline bool fwnode_is_gpiochip(struct fwnode_handle *fwnode)
--
2.50.1
next reply other threads:[~2026-10-21 14:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 14:55 Andy Shevchenko [this message]
2026-10-22 8:18 ` 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=20261021145543.567959-1-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=brgl@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®