linux-kernel - Re: [PATCH] pinctrl: tegra: refactor probe handling

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: <CACRpkdZQneBCOGp8oL2O4+J0OnOeW7NUHt2Eo7sKqQ_4jSGKLg@mail.gmail.com>
Date:	Fri, 13 Apr 2012 14:41:16 +0200
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Stephen Warren <swarren@...dotorg.org>
Cc:	Olof Johansson <olof@...om.net>, Colin Cross <ccross@...roid.com>,
	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
	linux-tegra@...r.kernel.org, Stephen Warren <swarren@...dia.com>
Subject: Re: [PATCH] pinctrl: tegra: refactor probe handling

On Wed, Apr 11, 2012 at 9:00 PM, Stephen Warren <swarren@...dotorg.org> wrote:

> From: Stephen Warren <swarren@...dia.com>
>
> Rather than having a single tegra-pinctrl driver that determines whether
> it's running on Tegra20 or Tegra30, instead have separate drivers for
> each that call into utility functions to implement the majority of the
> driver. This change is based on review feedback of the SPEAr pinctrl
> driver, which had originally copied to Tegra driver structure.
>
> This requires that the two drivers have unique names. Update a couple
> spots in arch/arm/mach-tegra for the name change.
>
> Signed-off-by: Stephen Warren <swarren@...dia.com>
> ---
> Linus, It'll be easiest for me to merge this through the Tegra tree, since
> the arch/arm changes depend on the patches there that switch to using the
> pinctrl driver. If you could ack this, it'd be great. Thanks.

Sure,
Acked-by: Linus Walleij <linus.walleij@...aro.org>

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/