Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752012Ab2KXRtJ (ORCPT ); Sat, 24 Nov 2012 12:49:09 -0500 Received: from avon.wwwdotorg.org ([70.85.31.133]:45837 "EHLO avon.wwwdotorg.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751864Ab2KXRtI (ORCPT ); Sat, 24 Nov 2012 12:49:08 -0500 Message-ID: <50B10883.5040101@nvidia.com> Date: Sat, 24 Nov 2012 10:48:51 -0700 From: Stephen Warren User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: Linus Walleij CC: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Shiraz Hashim , Viresh Kumar , Anmar Oueja , Grant Likely , Linus Walleij Subject: Re: [PATCH] gpiolib: rename pin range arguments References: <1353484243-6115-1-git-send-email-linus.walleij@stericsson.com> In-Reply-To: <1353484243-6115-1-git-send-email-linus.walleij@stericsson.com> X-Enigmail-Version: 1.4.4 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 722 Lines: 16 On 11/21/2012 12:50 AM, Linus Walleij wrote: > To be crystal clear on what the arguments mean in this > funtion dealing with both GPIO and PIN ranges with confusing > naming, we now have gpio_offset and pin_offset and we are > on the clear that these are offsets into the specific GPIO > and pin controller respectively. The GPIO chip itself will > of course keep track of the base offset into the global > GPIO number space. Reviewed-by: Stephen Warren -- 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/