[PATCH 1/2] regmap: Use int rather than size_t for lengths when logging blocks

From: Mark Brown
Date: Tue Aug 09 2011 - 10:35:29 EST


x86_64 warns as size_t is not an int.

Signed-off-by: Mark Brown <broonie@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
---
include/trace/events/regmap.h | 14 +++++++-------
1 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/include/trace/events/regmap.h b/include/trace/events/regmap.h
index 1c76f40..e35e37c 100644
--- a/include/trace/events/regmap.h
+++ b/include/trace/events/regmap.h
@@ -57,14 +57,14 @@ DEFINE_EVENT(regmap_reg, regmap_reg_read,

DECLARE_EVENT_CLASS(regmap_block,

- TP_PROTO(struct device *dev, unsigned int reg, size_t count),
+ TP_PROTO(struct device *dev, unsigned int reg, int count),

TP_ARGS(dev, reg, count),

TP_STRUCT__entry(
__string( name, dev_name(dev) )
__field( unsigned int, reg )
- __field( size_t, count )
+ __field( int, count )
),

TP_fast_assign(
@@ -75,33 +75,33 @@ DECLARE_EVENT_CLASS(regmap_block,

TP_printk("%s reg=%x count=%d", __get_str(name),
(unsigned int)__entry->reg,
- (size_t)__entry->count)
+ (int)__entry->count)
);

DEFINE_EVENT(regmap_block, regmap_hw_read_start,

- TP_PROTO(struct device *dev, unsigned int reg, size_t count),
+ TP_PROTO(struct device *dev, unsigned int reg, int count),

TP_ARGS(dev, reg, count)
);

DEFINE_EVENT(regmap_block, regmap_hw_read_done,

- TP_PROTO(struct device *dev, unsigned int reg, size_t count),
+ TP_PROTO(struct device *dev, unsigned int reg, int count),

TP_ARGS(dev, reg, count)
);

DEFINE_EVENT(regmap_block, regmap_hw_write_start,

- TP_PROTO(struct device *dev, unsigned int reg, size_t count),
+ TP_PROTO(struct device *dev, unsigned int reg, int count),

TP_ARGS(dev, reg, count)
);

DEFINE_EVENT(regmap_block, regmap_hw_write_done,

- TP_PROTO(struct device *dev, unsigned int reg, size_t count),
+ TP_PROTO(struct device *dev, unsigned int reg, int count),

TP_ARGS(dev, reg, count)
);
--
1.7.5.4

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/