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  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]
Date:	Fri, 23 May 2014 01:14:59 +0200
From:	Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>
To:	Linus Walleij <linus.walleij@...aro.org>
CC:	Antoine Tenart <antoine.tenart@...e-electrons.com>,
	Alexandre Belloni <alexandre.belloni@...e-electrons.com>,
	Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>,
	zhiming Xu <zmxu@...vell.com>,
	Jisheng Zhang <jszhang@...vell.com>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v4 0/7] ARM: berlin: add pinctrl support

On 05/23/2014 12:11 AM, Linus Walleij wrote:
> On Mon, May 19, 2014 at 7:36 PM, Sebastian Hesselbarth
> <sebastian.hesselbarth@...il.com> wrote:
> 
>> but can you please drop the Berlin pinctrl patches
>> and reconsider taking the reworked driver instead?
> 
> Sure I applied patches 1 thru 4 to the pin control tree.
> The rest you need to carry in some ARM SoC tree or
> similar.

Great, thanks. Having it in is a huge benefit as future device
drivers will depend on at least some pinctrl. Functionally it is
ok, Mike's request for clock node rework smashed my time schedule.

> I don't mind the driver being half-merged like this, because
> it means we can work on consolidating the utils code
> in the next cycle.

Sure, pinctrl properties consolidation is on my list for next
cycle.

Anyway, sorry for the late mess with it, I am still learning on
the first real arm/mach-maintainer cycle.

Sebastian
--
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/

Powered by blists - more mailing lists