From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751195AbdBBKHM (ORCPT ); Thu, 2 Feb 2017 05:07:12 -0500 Received: from mga11.intel.com ([192.55.52.93]:42232 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750970AbdBBKHJ (ORCPT ); Thu, 2 Feb 2017 05:07:09 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.33,324,1477983600"; d="scan'208";a="929315303" Date: Thu, 2 Feb 2017 12:07:02 +0200 From: Mika Westerberg To: Linus Walleij Cc: Boris Brezillon , Alexandre Courbot , Dmitry Torokhov , "linux-gpio@vger.kernel.org" , Linux Input , Bryan Wu , Richard Purdie , Jacek Anaszewski , "linux-leds@vger.kernel.org" , Tomi Valkeinen , "linux-fbdev@vger.kernel.org" , "linux-kernel@vger.kernel.org" , Russell King Subject: Re: [PATCH 1/2] gpio: Rename devm_get_gpiod_from_child() Message-ID: <20170202100702.GE2053@lahna.fi.intel.com> References: <20170131090432.72a1b1b8@bbrezillon> <20170131084447.GD8311@dtor-ws> <20170131100721.22c2388d@bbrezillon> <20170131091155.GH8311@dtor-ws> <20170131102424.7b68c0d4@bbrezillon> <20170131183936.GB13642@dtor-ws> <20170131204202.7b589ca6@bbrezillon> <20170201142228.053e2041@bbrezillon> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo User-Agent: Mutt/1.7.1 (2016-10-04) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Feb 01, 2017 at 03:51:06PM +0100, Linus Walleij wrote: > fwnode_get_named_gpiod() > devm_get_gpiod_from_child() > > Both are taking a fwnode as argument and the naming is as > inconsistent as it can be. > > Some more churn should be expected as a side > effect of naming this function wrong in the first place. > The fwnode API change was on fast-forward and mistakes > were made, also by me, mea culpa. The name fwnode_get_named_gpiod() tries to follow of_get_named_gpio() so that we can easily convert a driver to use fwnodes instead. The other function is named so because we look child fwnodes under a device. For that, yes certainly we could have invented a better name ;-)