Linus Torvalds wrote:For normal locks. But if you have N number of outstanding events you need to wait for the semaphore is the right primitive. And it seems there is a not high but non trivial number of places in the kernel who have a legitimate need for this. Ok so you just want to rename it. Fine for me. I always found up() and down() unintuitive anyways (but it's admittedly better than "P" and "V" which some other systems use) Because we still "counted completions" for some things and that's the same code? Rather i suspect the real problem is not the name, but just not sure it gets abused. That is largely more a review problem and as far as I can figure out basically all the usual reviewers take care of that anyways. But renaming it also probably wouldn't hurt. [IMHO I always thought we should have a maintained single "list of things for reviewers to watch out for" list somewhere] -Andi --
| Greg Kroah-Hartman | [PATCH 002/196] Chinese: rephrase English introduction in HOWTO |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Roland Dreier | Re: Integration of SCST in the mainstream Linux kernel |
git: | |
| Radu Rendec | htb parallelism on multi-core platforms |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | [GIT]: Networking |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
