From: Karl Mehltretter <kmehltretter@gmail.com>
To: Bartosz Golaszewski <brgl@kernel.org>
Cc: Karl Mehltretter <kmehltretter@gmail.com>,
Kent Gibson <warthog618@gmail.com>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] gpio: uapi: Fix gpio_v2_line_info_changed reference in kernel-doc
Date: Sat, 12 Sep 2026 00:40:10 +0200 [thread overview]
Message-ID: <20260911224010.10393-1-kmehltretter@gmail.com> (raw)
The gpio_v2_line_changed_type comment names the containing struct as
gpio_v2_line_changed. This was a typo in the original GPIO uAPI v2
documentation; the struct containing event_type is named
gpio_v2_line_info_changed.
Use the correct struct name.
Fixes: b53911aa872d ("gpio: uapi: define uAPI v2")
Assisted-by: LLM
Signed-off-by: Karl Mehltretter <kmehltretter@gmail.com>
---
include/uapi/linux/gpio.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/uapi/linux/gpio.h b/include/uapi/linux/gpio.h
index f7cb8ae87df72cc3f35b0619f3c3c95798009c5a..7e77bb6bfaeddb72d33e98a0171925f1cae686f4 100644
--- a/include/uapi/linux/gpio.h
+++ b/include/uapi/linux/gpio.h
@@ -232,7 +232,7 @@ struct gpio_v2_line_info {
};
/**
- * enum gpio_v2_line_changed_type - &struct gpio_v2_line_changed.event_type
+ * enum gpio_v2_line_changed_type - &struct gpio_v2_line_info_changed.event_type
* values
* @GPIO_V2_LINE_CHANGED_REQUESTED: line has been requested
* @GPIO_V2_LINE_CHANGED_RELEASED: line has been released
--
2.39.5 (Apple Git-154)
next reply other threads:[~2026-09-11 22:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 22:40 Karl Mehltretter [this message]
2026-09-12 12:51 ` [PATCH] gpio: uapi: Fix gpio_v2_line_info_changed reference in kernel-doc Andy Shevchenko
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=20260911224010.10393-1-kmehltretter@gmail.com \
--to=kmehltretter@gmail.com \
--cc=andy.shevchenko@gmail.com \
--cc=brgl@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=warthog618@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