linux-kernel - Re: [PATCH V4 REPOST 5/5] pinctrl: tegra: Add complete device tree support

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]

Message-ID: <4F8457F9.7090309@wwwdotorg.org>
Date:	Tue, 10 Apr 2012 09:55:37 -0600
From:	Stephen Warren <swarren@...dotorg.org>
To:	Linus Walleij <linus.walleij@...aro.org>
CC:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH V4 REPOST 5/5] pinctrl: tegra: Add complete device tree
 support

On 04/10/2012 02:25 AM, Linus Walleij wrote:
> On Wed, Apr 4, 2012 at 5:27 PM, Stephen Warren <swarren@...dotorg.org> wrote:
> 
>> From: Stephen Warren <swarren@...dia.com>
>>
>> Implement pinctrl_ops dt_node_to_map() and dt_free_map(). These allow
>> complete specification of the desired pinmux configuration using device
>> tree.
>>
>> Signed-off-by: Stephen Warren <swarren@...dia.com>
>> Acked-by: Dong Aisheng <dong.aisheng@...aro.org>
>> ---
>> v3: Rebase on of_property_for_each_string() API changes.
>>    Improve DT parsing so it only calls krealloc() on the top-level map
>>    table once per subnode, rather than once per subnode/pin combination.
>> v2: Rebase on of_property_for_each_string() API changes.
> 
> Applied to pinctrl, thanks!
> Linus Walleij

Great.

Is your pinctrl for-next branch considered "stable" (i.e. it won't ever
be rebased) at least up to commit a57be23 "pinctrl: tegra: Add complete
device tree support"?

If so, I'll use it as a base for the Tegra GPIO and pinmux rework branch.

Thanks.
--
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/