From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758987Ab2CBRlM (ORCPT ); Fri, 2 Mar 2012 12:41:12 -0500 Received: from hqemgate03.nvidia.com ([216.228.121.140]:15710 "EHLO hqemgate03.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756877Ab2CBRlK convert rfc822-to-8bit (ORCPT ); Fri, 2 Mar 2012 12:41:10 -0500 X-PGP-Universal: processed; by hqnvupgp05.nvidia.com on Fri, 02 Mar 2012 09:41:07 -0800 From: Stephen Warren To: Stephen Warren , Linus Walleij , "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" CC: Grant Likely , Barry Song <21cnbao@gmail.com>, Shawn Guo , Thomas Abraham , Dong Aisheng , Rajendra Nayak , Haojian Zhuang , Linus Walleij Date: Fri, 2 Mar 2012 09:41:04 -0800 Subject: RE: [PATCH] pinctrl: resurrect verbose pinmux-pins Thread-Topic: [PATCH] pinctrl: resurrect verbose pinmux-pins Thread-Index: Acz4lixCNm7g+kafTBifQmUDymm0IwAAk6OgAAC7AsA= Message-ID: <74CDBE0F657A3D45AFBB94109FB122FF17BE861991@HQMAIL01.nvidia.com> References: <1330705873-10798-1-git-send-email-linus.walleij@stericsson.com> <74CDBE0F657A3D45AFBB94109FB122FF17BE861978@HQMAIL01.nvidia.com> In-Reply-To: <74CDBE0F657A3D45AFBB94109FB122FF17BE861978@HQMAIL01.nvidia.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Stephen Warren wrote at Friday, March 02, 2012 10:22 AM: > Linus Walleij wrote at riday, March 02, 2012 9:31 AM: > > From: Linus Walleij > > > > This reintroduces the verbosity in the pinmux-pins file, now this > > file will list all pins, their names, owning device (and if it's > > a hog) and also in applicable cases the function and group making > > use of that pin right now. > > > > Signed-off-by: Linus Walleij > > It'd be nice if we could defer this fix until after all the API rework, > because it'll cause all kinds of conflicts otherwise. Oh, I see this patch is in your for-next branch already before I had a chance to comment on it. I guess I'll have write a patch to convert the removed struct type to char*s and rebase on top of it:-( -- nvpublic