Re: [PATCH] locking: type cleanup when accessing fast_read_ctr

[Oleg Nesterov]

On 05/19, Nicholas Mc Guire wrote:
>
> I assumed it would not matter but did not see a simple way of getting it
> type clean with unsigned either mainly due to the atomic_t being int and
> val in update_fast_ctr() being passed as -1.

Perhaps clear_fast_ctr() should have a comment to explain why it returns
"int"... even if "unsigned" should work too.

Please see https://lkml.org/lkml/2012/11/2/346

Oleg.

--
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/