summaryrefslogtreecommitdiff
path: root/Documentation/block
diff options
context:
space:
mode:
authorMatthew Wilcox <matthew.r.wilcox@intel.com>2016-03-06 23:27:26 -0500
committerAl Viro <viro@zeniv.linux.org.uk>2016-06-30 23:30:52 -0400
commitf4e6d844bdc142322905d137a9e44e07eee43c5c (patch)
tree3feaa4a6dd2e88ddaa8867d645f9ed2346e7b38b /Documentation/block
parentd4c91a8f7e5514a1e9cd37b453fda0dedfa8045d (diff)
Remove last traces of ->sync_page
Commit 7eaceaccab5f removed ->sync_page, but a few mentions of it still existed in documentation and comments, Signed-off-by: Matthew Wilcox <matthew.r.wilcox@intel.com> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Diffstat (limited to 'Documentation/block')
-rw-r--r--Documentation/block/biodoc.txt3
1 files changed, 1 insertions, 2 deletions
diff --git a/Documentation/block/biodoc.txt b/Documentation/block/biodoc.txt
index 5be8a7f4cc7f..026d13362aca 100644
--- a/Documentation/block/biodoc.txt
+++ b/Documentation/block/biodoc.txt
@@ -1024,8 +1024,7 @@ could be on demand. For example wait_on_buffer sets the unplugging going
through sync_buffer() running blk_run_address_space(mapping). Or the caller
can do it explicity through blk_unplug(bdev). So in the read case,
the queue gets explicitly unplugged as part of waiting for completion on that
-buffer. For page driven IO, the address space ->sync_page() takes care of
-doing the blk_run_address_space().
+buffer.
Aside:
This is kind of controversial territory, as it's not clear if plugging is