Il 13/08/2013 11:09, Jan Kiszka ha scritto: >>>> >>> >>> >> >>> >> As the usage pattern is >>> >> >>> >> seqlock_read_begin() >>> >> do >>> >> ... >>> >> while (seqlock_read_check()) >>> >> >>> >> I would suggest to call the latter seqlock_read_retry(), just like the >>> >> kernel does. >>> >> >> > I think it contains the meaning of check-success-or-retry. So may >> > check be nicer? > "Check" alone has no obvious semantic for me, therefore "retry".
I agree. I was writing the patch without looking at any Linux code (just to be safe since it's GPLv2-only) and misremembered the name of the API. Paolo
