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>

1 files changed, 1 insertions, 4 deletions

diff --git a/block/blk-core.c b/block/blk-core.c
index 8b4a0af7d69f..7e0fab53e930 100644
--- a/block/blk-core.c
+++ b/block/blk-core.c
@@ -1082,16 +1082,13 @@ void init_request_from_bio(struct request *req, struct bio *bio)
         if (bio_failfast_driver(bio))
                 req->cmd_flags |= REQ_FAILFAST_DRIVER;
 
-        /*
-         * REQ_BARRIER implies no merging, but lets make it explicit
-         */
         if (unlikely(bio_discard(bio))) {
                 req->cmd_flags |= REQ_DISCARD;
                 if (bio_barrier(bio))
                         req->cmd_flags |= REQ_SOFTBARRIER;
                 req->q->prepare_discard_fn(req->q, req);
         } else if (unlikely(bio_barrier(bio)))
-                req->cmd_flags |= (REQ_HARDBARRIER | REQ_NOMERGE);
+                req->cmd_flags |= REQ_HARDBARRIER;
 
         if (bio_sync(bio))
                 req->cmd_flags |= REQ_RW_SYNC;