linux-kernel - Re: [PATCH] gpio: rename gpio_lock_as_irq to gpiochip_lock_as

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 for Android: free password hash cracker in your pocket

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

Message-ID: <CACRpkdbFYi3O7ONeo-Z1iA_ZkL-YSekL7hDz9Dj1eHdKe5y8Tg@mail.gmail.com>
Date:	Tue, 28 Oct 2014 17:32:14 +0100
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Alexandre Courbot <acourbot@...dia.com>
Cc:	"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Alexandre Courbot <gnurou@...il.com>
Subject: Re: [PATCH] gpio: rename gpio_lock_as_irq to gpiochip_lock_as_irq

On Thu, Oct 23, 2014 at 10:27 AM, Alexandre Courbot <acourbot@...dia.com> wrote:

> This function actually operates on a gpio_chip, so its prefix should
> reflect that fact for consistency with other functions defined in
> gpio/driver.h.
>
> Signed-off-by: Alexandre Courbot <acourbot@...dia.com>
> ---
> Just a consistency change ; hopefully we can slip this under the GPIO
> tree without getting acked-bys from each subsystem.

OK patch applied, hope I don't get too much breakage from new
drivers using the call. Maybe I'll have to apply the patch to
both the GPIO and pin control subsystem :-P

Yours,
Linus Walleij
--
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/