Re: [PATCH 2/2] mfd: max77693: reorder params in API for regmap consistency

2013-11-08 Thread Lee Jones
On Fri, 08 Nov 2013, Krzysztof Kozlowski wrote: > The last two parameters of certain register access functions were in > different order than regmap API. This was confusing and error-prone. > > Reorder parameters for register access API to match regmap API: > - max77693_bulk_read() reorder

[PATCH 2/2] mfd: max77693: reorder params in API for regmap consistency

2013-11-08 Thread Krzysztof Kozlowski
The last two parameters of certain register access functions were in different order than regmap API. This was confusing and error-prone. Reorder parameters for register access API to match regmap API: - max77693_bulk_read() reorder count and buf, - max77693_bulk_write() reorder count and buf,

[PATCH 2/2] mfd: max77693: reorder params in API for regmap consistency

2013-11-08 Thread Krzysztof Kozlowski
The last two parameters of certain register access functions were in different order than regmap API. This was confusing and error-prone. Reorder parameters for register access API to match regmap API: - max77693_bulk_read() reorder count and buf, - max77693_bulk_write() reorder count and buf,

Re: [PATCH 2/2] mfd: max77693: reorder params in API for regmap consistency

2013-11-08 Thread Lee Jones
On Fri, 08 Nov 2013, Krzysztof Kozlowski wrote: The last two parameters of certain register access functions were in different order than regmap API. This was confusing and error-prone. Reorder parameters for register access API to match regmap API: - max77693_bulk_read() reorder count and