Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752250Ab3FJMwP (ORCPT ); Mon, 10 Jun 2013 08:52:15 -0400 Received: from mail-ob0-f169.google.com ([209.85.214.169]:42050 "EHLO mail-ob0-f169.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751034Ab3FJMwO convert rfc822-to-8bit (ORCPT ); Mon, 10 Jun 2013 08:52:14 -0400 MIME-Version: 1.0 In-Reply-To: <201306090159.05383.heiko@sntech.de> References: <201306090159.05383.heiko@sntech.de> Date: Mon, 10 Jun 2013 14:52:13 +0200 Message-ID: Subject: Re: [PATCH 0/2] pinctrl: common handling of generic pinconfig props in dt From: Linus Walleij To: =?ISO-8859-1?Q?Heiko_St=FCbner?= Cc: Patrice Chotard , "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1074 Lines: 27 On Sun, Jun 9, 2013 at 1:59 AM, Heiko St?bner wrote: > following your suggestions for a common handling of things like pulls in dt, > I've come up with the following solution - hopefully I've gotten the correct > meaning of your explanaitions. > > It handles all the pinconfigs that either ignore the argument, or have very > simple one, like PIN_CONFIG_OUTPUT does. OK patches applied. It needs some rough fixes like NULL check on kmalloc() but it'll do for a starter. Now I can tell everyone to use this and refer to it. > I've also attached my current rockchip pinctrl driver to show how it is using > this currently. OK I might just merge it. If you take the rest of the patches through ARM SoC they will need to pull in my tree anyway if it's intended to go in this merge window. Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/