linux-kernel - [PATCH 0/4] gpiolib: some fixup patches

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 13 Feb 2013 16:02:58 +0900
From:	Alexandre Courbot <gnurou@...il.com>
To:	Grant Likely <grant.likely@...retlab.ca>,
	Linus Walleij <linus.walleij@...aro.org>
Cc:	linux-kernel@...r.kernel.org, gnurou@...il.com
Subject: [PATCH 0/4] gpiolib: some fixup patches

This short series is a fixup to patch 6/9 of my previous series ("gpiolib: use 
descriptors internally"), which mainly addresses issues raised by Linus W. in 
this patch and a few other minor ones caught while proof-reading gpiolib.

First patch is the most significant. It mostly avoids oopses when passing an 
invalid GPIO to some functions. Also gpio_get/set_value*() now return 0 when 
given an invalid GPIO number instead of oopsing. I tend to think that's an 
improvement, but if it's not please let me know.

Ideally these patches should be melded into the above-mentioned patch since 
they were intended to become a new revision, but I leave that decision to 
Grant's discretion.

This patchset has been thoroughly tested on Tegra 2/Ventana with a GPIO 
backlight driver and the sysfs interface.

Alexandre Courbot (4):
  gpiolib: check descriptors validity before use
  gpiolib: use const parameters when possible
  gpiolib: move comment to right function
  gpiolib: rename local offset variables to "hwgpio"

 drivers/gpio/gpiolib.c | 165 ++++++++++++++++++++++++++-----------------------
 1 file changed, 87 insertions(+), 78 deletions(-)

-- 
1.8.1.3

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/