[FSAIO][PATCH 2/8] Rename __lock_page to lock_page_slow

2006-12-28 Thread Suparna Bhattacharya
In order to allow for interruptible and asynchronous versions of lock_page in conjunction with the wait_on_bit changes, we need to define low-level lock page routines which take an additional argument, i.e a wait queue entry and may return non-zero status, e.g -EINTR, -EIOCBRETRY, -EWOULDBLOCK

[FSAIO][PATCH 2/8] Rename __lock_page to lock_page_slow

2006-12-28 Thread Suparna Bhattacharya
In order to allow for interruptible and asynchronous versions of lock_page in conjunction with the wait_on_bit changes, we need to define low-level lock page routines which take an additional argument, i.e a wait queue entry and may return non-zero status, e.g -EINTR, -EIOCBRETRY, -EWOULDBLOCK