| 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
| ||
|
Date: Thu, 10 Oct 2013 17:35:44 +0200 From: Linus Walleij <linus.walleij@...aro.org> To: Tony Lindgren <tony@...mide.com> Cc: "linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>, Grygorii Strashko <grygorii.strashko@...com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Peter Ujfalusi <peter.ujfalusi@...com>, Prakash Manjunathappa <prakash.pm@...com>, Haojian Zhuang <haojian.zhuang@...aro.org>, Linux-OMAP <linux-omap@...r.kernel.org>, Roger Quadros <rogerq@...com> Subject: Re: [PATCH 3/6] pinctrl: single: Prepare for supporting SoC specific features On Wed, Oct 9, 2013 at 5:10 PM, Tony Lindgren <tony@...mide.com> wrote: > I was thinking I'll set up an immutable branch for the three > pinctrl patches against -rc4 then both you and I can merge > them in as needed. Does that work for you? Hm it's fair enough to have them in your tree if they do not collide ... especially if you want to do some of my suggested follow-up moving the ioring handling down into pinctrl-single on top of that. > I can also do a test merge with pinctrl/for-next also to make > sure there are no conflicts. Sure, as long as that works you should be safe. 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/
Powered by blists - more mailing lists