[PATCH 1/2] SCHED: remove proliferation of wait_on_bit action functions.

The current "wait_on_bit" interface requires an 'action' function to be provided which does the actual waiting. There are over 20 such functions, many of them identical. Most cases can be satisfied by one of just two functions, one which uses io_schedule() and one which just uses schedule(). So:

[PATCH 1/2] SCHED: remove proliferation of wait_on_bit action functions.

The current wait_on_bit interface requires an 'action' function to be provided which does the actual waiting. There are over 20 such functions, many of them identical. Most cases can be satisfied by one of just two functions, one which uses io_schedule() and one which just uses schedule(). So:

Re: [PATCH 1/2] SCHED: remove proliferation of wait_on_bit action functions.

Acked-by: David Howells (fscache, keys) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Re: [PATCH 1/2] SCHED: remove proliferation of wait_on_bit action functions.

Acked-by: David Howells dhowe...@redhat.com (fscache, keys) -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at

[PATCH 1/2] SCHED: remove proliferation of wait_on_bit action functions.

The current "wait_on_bit" interface requires an 'action' function to be provided which does the actual waiting. There are over 20 such functions, many of them identical. Most cases can be satisfied by one of just two functions, one which uses io_schedule() and one which just uses schedule(). So:

[PATCH 1/2] SCHED: remove proliferation of wait_on_bit action functions.

The current wait_on_bit interface requires an 'action' function to be provided which does the actual waiting. There are over 20 such functions, many of them identical. Most cases can be satisfied by one of just two functions, one which uses io_schedule() and one which just uses schedule(). So: