From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934312AbcATBPy (ORCPT ); Tue, 19 Jan 2016 20:15:54 -0500 Received: from mail.kmu-office.ch ([178.209.48.109]:60017 "EHLO mail.kmu-office.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934268AbcATBP3 (ORCPT ); Tue, 19 Jan 2016 20:15:29 -0500 From: Stefan Agner To: broonie@kernel.org Cc: linux-kernel@vger.kernel.org, Stefan Agner Subject: [PATCH] regmap: clairify meaning of max_register Date: Tue, 19 Jan 2016 17:14:39 -0800 Message-Id: <1453252479-19493-1-git-send-email-stefan@agner.ch> X-Mailer: git-send-email 2.7.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org The exact meaning of max_register is not entierly clear. Follow the common wording and use "address" instead of "index". Signed-off-by: Stefan Agner --- include/linux/regmap.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/include/linux/regmap.h b/include/linux/regmap.h index 1839434..27aaac9 100644 --- a/include/linux/regmap.h +++ b/include/linux/regmap.h @@ -162,7 +162,7 @@ typedef void (*regmap_unlock)(void *); * This field is a duplicate of a similar file in * 'struct regmap_bus' and serves exact same purpose. * Use it only for "no-bus" cases. - * @max_register: Optional, specifies the maximum valid register index. + * @max_register: Optional, specifies the maximum valid register address. * @wr_table: Optional, points to a struct regmap_access_table specifying * valid ranges for write access. * @rd_table: As above, for read access. -- 2.7.0