linux-kernel - Re: [PATCH] gpio: make GPIO_OMAP bool instead of tristate

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-prev] [day] [month] [year] [list]

Message-ID: <CACRpkdahobgJwcaU2L-Fm6pEonjZt9ogUZVD4t_iVmP9M-Nv+A@mail.gmail.com>
Date:	Fri, 16 Oct 2015 17:08:25 +0200
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Sudip Mukherjee <sudipm.mukherjee@...il.com>
Cc:	Alexandre Courbot <gnurou@...il.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
	Tony Lindgren <tony@...mide.com>,
	Austin Schuh <austin@...oton-tech.com>,
	Grygorii Strashko <grygorii.strashko@...com>,
	Santosh Shilimkar <ssantosh@...nel.org>
Subject: Re: [PATCH] gpio: make GPIO_OMAP bool instead of tristate

On Tue, Oct 6, 2015 at 2:01 PM, Sudip Mukherjee
<sudipm.mukherjee@...il.com> wrote:

> While building arm allmodconfig the build fails with the error:
> ERROR: "handle_bad_irq" [drivers/gpio/gpio-omap.ko] undefined!
>
> The build breaks as handle_bad_irq is not exported for module use.
>
> Fixes: 450fa54cfd66 ("gpio: omap: convert to use generic irq handler")
> Cc: Tony Lindgren <tony@...mide.com>
> Cc: Austin Schuh <austin@...oton-tech.com>
> Cc: Grygorii Strashko <grygorii.strashko@...com>
> Cc: Santosh Shilimkar <ssantosh@...nel.org>
> Signed-off-by: Sudip Mukherjee <sudip@...torindia.org>

Fixed upstream. Dropping this patch.

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/