[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160109133918.GC26660@infradead.org>
Date: Sat, 9 Jan 2016 05:39:18 -0800
From: Christoph Hellwig <hch@...radead.org>
To: mchristi@...hat.com
Cc: linux-f2fs-devel@...ts.sourceforge.net, linux-ext4@...r.kernel.org,
konrad.wilk@...cle.com, drbd-dev@...ts.linbit.com,
philipp.reisner@...bit.com, lars.ellenberg@...bit.com,
linux-raid@...r.kernel.org, dm-devel@...hat.com,
linux-fsdevel@...r.kernel.org, linux-bcache@...r.kernel.org,
linux-block@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-scsi@...r.kernel.org, linux-mtd@...ts.infradead.org,
target-devel@...r.kernel.org, linux-btrfs@...r.kernel.org,
osd-dev@...n-osd.org, xfs@....sgi.com, ocfs2-devel@....oracle.com
Subject: Re: [PATCH 26/35] block: set op to REQ_OP
> @@ -1149,10 +1151,12 @@ static struct request *__get_request(struct request_list *rl, int rw_flags,
>
> blk_rq_init(q, rq);
> blk_rq_set_rl(rq, rl);
> - rq->cmd_flags = rw_flags | REQ_ALLOCED;
> + /* tmp compat - allow users to check either one for the op */
> + rq->cmd_flags = op | op_flags | REQ_ALLOCED;
This one is still left after the whole series is applied, seems like
the hunk to remove it again got lost somewhere.
Powered by blists - more mailing lists