From: Viresh Kumar <viresh.kumar@linaro.org>
To: Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
linux-gpio@vger.kernel.org, Kent Gibson <warthog618@gmail.com>
Subject: [PATCH 1/2] libgpiod: Fix ioctl number for gpiod_line_request_reconfigure_lines()
Date: Fri, 26 Nov 2021 14:37:04 +0530 [thread overview]
Message-ID: <ce3d189ec1f04092f7edc56c9a1f6534b60d6a14.1637917008.git.viresh.kumar@linaro.org> (raw)
In-Reply-To: <cover.1637917008.git.viresh.kumar@linaro.org>
The ioctl number used for gpiod_line_request_reconfigure_lines() is
incorrect written as GPIO_V2_LINE_GET_VALUES_IOCTL instead of
GPIO_V2_LINE_SET_CONFIG_IOCTL. Fix it.
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
---
lib/line-request.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/line-request.c b/lib/line-request.c
index 8008b89c7e65..0ac4ec89408e 100644
--- a/lib/line-request.c
+++ b/lib/line-request.c
@@ -197,7 +197,7 @@ gpiod_line_request_reconfigure_lines(struct gpiod_line_request *request,
if (ret)
return ret;
- ret = ioctl(request->fd, GPIO_V2_LINE_GET_VALUES_IOCTL, &cfgbuf);
+ ret = ioctl(request->fd, GPIO_V2_LINE_SET_CONFIG_IOCTL, &cfgbuf);
if (ret)
return ret;
--
2.31.1.272.g89b43f80a514
next prev parent reply other threads:[~2021-11-26 9:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-26 9:07 [PATCH 0/2] libgpiod: Minor fixups for 2.0 bindings Viresh Kumar
2021-11-26 9:07 ` Viresh Kumar [this message]
2021-11-26 9:07 ` [PATCH 2/2] libgpiod: Remove dummy declaration gpiod_line_config_get_event_clock() Viresh Kumar
2021-12-03 14:39 ` Bartosz Golaszewski
2021-12-03 10:58 ` [PATCH 0/2] libgpiod: Minor fixups for 2.0 bindings Bartosz Golaszewski
2021-12-03 11:14 ` Viresh Kumar
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=ce3d189ec1f04092f7edc56c9a1f6534b60d6a14.1637917008.git.viresh.kumar@linaro.org \
--to=viresh.kumar@linaro.org \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=vincent.guittot@linaro.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;
as well as URLs for NNTP newsgroup(s).