From: Wolfram Sang <wsa+renesas@sang-engineering.com> To: linux-gpio@vger.kernel.org Cc: linux-renesas-soc@vger.kernel.org, Wolfram Sang <wsa+renesas@sang-engineering.com>, dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org, linux-pwm@vger.kernel.org, linux-serial@vger.kernel.org Subject: [PATCH 0/3] tree-wide: don't use GPIOF_* with gpiod_get_direction Date: Sun, 14 Jan 2018 22:07:07 +0100 [thread overview] Message-ID: <20180114210711.13863-1-wsa+renesas@sang-engineering.com> (raw) The documentation was wrong, gpiod_get_direction() returns 0/1 instead of the GPIOF_* flags. The docs were fixed with commit 94fc73094abe47 ("gpio: correct docs about return value of gpiod_get_direction"). Now, fix the users who got it as wrong as I did when developing bus recovery for the R-Car I2C driver. We get rid of two users of 'linux/gpio.h' this way :) Only build tested due to no hardware. Wolfram Sang (3): extcon: int3496: don't use GPIOF_* with gpiod_get_direction serial: mxs-auart: don't use GPIOF_* with gpiod_get_direction backlight: pwm_bl: don't use GPIOF_* with gpiod_get_direction drivers/extcon/extcon-intel-int3496.c | 4 ++-- drivers/tty/serial/mxs-auart.c | 3 +-- drivers/video/backlight/pwm_bl.c | 6 +++--- 3 files changed, 6 insertions(+), 7 deletions(-) -- 2.11.0
WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <wsa+renesas@sang-engineering.com> To: linux-gpio@vger.kernel.org Cc: linux-renesas-soc@vger.kernel.org, Wolfram Sang <wsa+renesas@sang-engineering.com>, dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org, linux-pwm@vger.kernel.org, linux-serial@vger.kernel.org Subject: [PATCH 0/3] tree-wide: don't use GPIOF_* with gpiod_get_direction Date: Sun, 14 Jan 2018 21:07:07 +0000 [thread overview] Message-ID: <20180114210711.13863-1-wsa+renesas@sang-engineering.com> (raw) The documentation was wrong, gpiod_get_direction() returns 0/1 instead of the GPIOF_* flags. The docs were fixed with commit 94fc73094abe47 ("gpio: correct docs about return value of gpiod_get_direction"). Now, fix the users who got it as wrong as I did when developing bus recovery for the R-Car I2C driver. We get rid of two users of 'linux/gpio.h' this way :) Only build tested due to no hardware. Wolfram Sang (3): extcon: int3496: don't use GPIOF_* with gpiod_get_direction serial: mxs-auart: don't use GPIOF_* with gpiod_get_direction backlight: pwm_bl: don't use GPIOF_* with gpiod_get_direction drivers/extcon/extcon-intel-int3496.c | 4 ++-- drivers/tty/serial/mxs-auart.c | 3 +-- drivers/video/backlight/pwm_bl.c | 6 +++--- 3 files changed, 6 insertions(+), 7 deletions(-) -- 2.11.0
next reply other threads:[~2018-01-14 21:07 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-01-14 21:07 Wolfram Sang [this message] 2018-01-14 21:07 ` [PATCH 0/3] tree-wide: don't use GPIOF_* with gpiod_get_direction Wolfram Sang 2018-01-14 21:07 ` [PATCH 1/3] extcon: int3496: " Wolfram Sang 2018-01-14 21:07 ` [PATCH 2/3] serial: mxs-auart: " Wolfram Sang 2018-01-14 21:07 ` [PATCH 3/3] backlight: pwm_bl: " Wolfram Sang 2018-01-14 21:07 ` Wolfram Sang 2018-01-15 10:13 ` Daniel Thompson 2018-04-16 9:11 ` Lee Jones 2018-04-16 9:11 ` Lee Jones 2018-04-16 9:11 ` Lee Jones
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=20180114210711.13863-1-wsa+renesas@sang-engineering.com \ --to=wsa+renesas@sang-engineering.com \ --cc=dri-devel@lists.freedesktop.org \ --cc=linux-fbdev@vger.kernel.org \ --cc=linux-gpio@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-pwm@vger.kernel.org \ --cc=linux-renesas-soc@vger.kernel.org \ --cc=linux-serial@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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.