| commit | e4025f6c21f1389696c069be2dc647f364925c45 | [log] [tgz] |
|---|---|---|
| author | Tejun Heo <tj@kernel.org> | Thu Apr 23 11:05:17 2009 +0900 |
| committer | Jens Axboe <jens.axboe@oracle.com> | Tue Apr 28 07:37:33 2009 +0200 |
| tree | 4d7ee21062293c9a9d398063c22339b47f581283 | |
| parent | a7f557923441186a3cdbabc54f1bcacf42b63bf5 [diff] |
block: don't set REQ_NOMERGE unnecessarily RQ_NOMERGE_FLAGS already clears defines which REQ flags aren't mergeable. There is no reason to specify it superflously. It only adds to confusion. Don't set REQ_NOMERGE for barriers and requests with specific queueing directive. REQ_NOMERGE is now exclusively used by the merging code. [ Impact: cleanup ] Signed-off-by: Tejun Heo <tj@kernel.org>