linux-kernel - Re: [PATCH] gpio: xilinx: Drop architecture dependencies

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

Date:	Mon, 19 Oct 2015 10:52:02 -0700
From:	Moritz Fischer <moritz.fischer@...us.com>
To:	Soren Brinkmann <soren.brinkmann@...inx.com>
Cc:	Linus Walleij <linus.walleij@...aro.org>,
	Alexandre Courbot <gnurou@...il.com>,
	linux-kernel@...r.kernel.org, linux-gpio@...r.kernel.org,
	Zubair Lutfullah Kakakhel <Zubair.Kakakhel@...tec.com>,
	Lars-Peter Clausen <lars@...afoo.de>
Subject: Re: [PATCH] gpio: xilinx: Drop architecture dependencies

Acked-by: Moritz Fischer <moritz.fischer@...us.com>

On Mon, Oct 19, 2015 at 10:42 AM, Soren Brinkmann
<soren.brinkmann@...inx.com> wrote:
> The driver does not have any real architecture dependencies. To avoid
> listing each architecture that might use this driver on some
> FPGA-enabled platform, drop these dependencies.
>
> Signed-off-by: Soren Brinkmann <soren.brinkmann@...inx.com>
> ---
>  drivers/gpio/Kconfig | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpio/Kconfig b/drivers/gpio/Kconfig
> index 63000b1f9da8..45dfeef6018f 100644
> --- a/drivers/gpio/Kconfig
> +++ b/drivers/gpio/Kconfig
> @@ -506,7 +506,7 @@ config GPIO_XGENE_SB
>
>  config GPIO_XILINX
>         tristate "Xilinx GPIO support"
> -       depends on OF_GPIO && (PPC || MICROBLAZE || ARCH_ZYNQ || X86)
> +       depends on OF_GPIO
>         help
>           Say yes here to support the Xilinx FPGA GPIO device
>
> --
> 2.6.2.3.ga463a5b
>
--
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/