[<prev] [next>] [day] [month] [year] [list]
Message-Id: <1312853089-25803-1-git-send-email-broonie@opensource.wolfsonmicro.com>
Date: Tue, 9 Aug 2011 10:24:49 +0900
From: Mark Brown <broonie@...nsource.wolfsonmicro.com>
To: linux-kernel@...r.kernel.org
Cc: patches@...nsource.wolfsonmicro.com,
Mark Brown <broonie@...nsource.wolfsonmicro.com>
Subject: [PATCH] regmap: Fix kerneldoc errors for regmap
Signed-off-by: Mark Brown <broonie@...nsource.wolfsonmicro.com>
---
include/linux/regmap.h | 18 +++++++++---------
1 files changed, 9 insertions(+), 9 deletions(-)
diff --git a/include/linux/regmap.h b/include/linux/regmap.h
index c878a4b..4de137b 100644
--- a/include/linux/regmap.h
+++ b/include/linux/regmap.h
@@ -27,15 +27,15 @@ struct spi_device;
* @val_bits: Number of bits in a register value, mandatory.
*
* @max_register: Optional, specifies the maximum valid register index.
- * @writeable_register: Optional callback returning true if the register
- * can be written to.
- * @readable_register: Optional callback returning true if the register
- * can be read from.
- * @volatile_register: Optional callback returning true if the register
- * value can't be cached.
- * @precious_register: Optional callback returning true if the rgister
- * should not be read outside of a call from the driver
- * (eg, a clear on read interrupt status register).
+ * @writeable_reg: Optional callback returning true if the register
+ * can be written to.
+ * @readable_reg: Optional callback returning true if the register
+ * can be read from.
+ * @volatile_reg: Optional callback returning true if the register
+ * value can't be cached.
+ * @precious_reg: Optional callback returning true if the rgister
+ * should not be read outside of a call from the driver
+ * (eg, a clear on read interrupt status register).
*/
struct regmap_config {
int reg_bits;
--
1.7.5.4
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists