From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S938588AbcIHM3O (ORCPT ); Thu, 8 Sep 2016 08:29:14 -0400 Received: from mail-it0-f41.google.com ([209.85.214.41]:37496 "EHLO mail-it0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752429AbcIHM3M (ORCPT ); Thu, 8 Sep 2016 08:29:12 -0400 MIME-Version: 1.0 In-Reply-To: <1473337655.11323.94.camel@linux.intel.com> References: <1473331702-26711-1-git-send-email-bgolaszewski@baylibre.com> <1473331702-26711-7-git-send-email-bgolaszewski@baylibre.com> <1473337655.11323.94.camel@linux.intel.com> From: Bartosz Golaszewski Date: Thu, 8 Sep 2016 14:29:11 +0200 Message-ID: Subject: Re: [PATCH v5 6/6] gpio: pca953x: make the define names consistent To: Andy Shevchenko Cc: Linus Walleij , Alexandre Courbot , Vignesh R , Yong Li , Geert Uytterhoeven , linux-gpio , LKML Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 2016-09-08 14:27 GMT+02:00 Andy Shevchenko : > On Thu, 2016-09-08 at 12:48 +0200, Bartosz Golaszewski wrote: >> The register offset defines for the pca953x and pca957x expander >> families should have the same names to better reflect their similar >> purposes. > > > > >> chip->regs = &pca957x_regs; >> >> - ret = pca953x_read_regs(chip, PCA957X_OUT, chip->reg_output); >> + ret = pca953x_read_regs(chip, PCA957X_OUTPUT, chip- >> >reg_output); >> if (ret) >> goto out; >> - ret = pca953x_read_regs(chip, PCA957X_CFG, chip- >> >reg_direction); >> + ret = pca953x_read_regs(chip, PCA957X_DIRECTION, chip- >> >reg_direction); > > Bu we may use chip->regs->direction here, right? And output before. > Yes, though it should go into patch 1/6. Thanks, Bartosz