summaryrefslogtreecommitdiff
path: root/include/linux/blkdev.h
diff options
context:
space:
mode:
authorJens Axboe <axboe@suse.de>2002-10-27 17:16:39 -0800
committerJens Axboe <axboe@suse.de>2002-10-27 17:16:39 -0800
commitc5868eb784c333e89aa404ac4936a3e29f224303 (patch)
tree1c58e5d0bc2f3777aaceba901d11e4bab88031f9 /include/linux/blkdev.h
parentad519c6902fb66990ad206cdf2c38da259f0dee9 (diff)
[PATCH] queue last_merge hint cleanup
Cleanup the last_merge logic. There are two reasons for clearing last_merge when we are dealing with integrity, and these are: o Clear when handing the request to the driver, so we don't merge on a started request. o Clear when a request is taken off the list. This cannot be done from the driver (above case would already have been hit), but it can happen when we merge two requests. This makes it a lot nicer, it was always peculiar how we cleared in put_request.
Diffstat (limited to 'include/linux/blkdev.h')
0 files changed, 0 insertions, 0 deletions