On Mon, 12 Feb 2007, Christopher Li wrote:
>
> > - it shows the *programmer* that the function is doing somethign
> > "strange" (not really strange, but still: it's basically a fairly
> > readable way that it's doing locking in a weird way).
>
> Should the function declare in the header file has that as well?
Yes.
> When call one of those functions, it can know that function will change
> context. That might be a way to solve the problem that some of the
> spinlock function is not a inline function at all.
I thought we did that already. I'm fairly sure I had this working at some
point - exactly by having the calls just add up the (known) lock/unlock
offsets.
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
