Commit df56d228 authored by Matthew Wilcox (Oracle)'s avatar Matthew Wilcox (Oracle) Committed by Andrew Morton

hfs: really remove hfs_writepage

The earlier commit to remove hfs_writepage only removed it from one of the
aops.  Remove it from the btree_aops as well.

Link: https://lkml.kernel.org/r/20231215200245.748418-8-willy@infradead.orgSigned-off-by: default avatarMatthew Wilcox (Oracle) <willy@infradead.org>
Reviewed-by: default avatarJens Axboe <axboe@kernel.dk>
Cc: Christoph Hellwig <hch@lst.de>
Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
parent 3a44d305
...@@ -29,11 +29,6 @@ static const struct inode_operations hfs_file_inode_operations; ...@@ -29,11 +29,6 @@ static const struct inode_operations hfs_file_inode_operations;
#define HFS_VALID_MODE_BITS (S_IFREG | S_IFDIR | S_IRWXUGO) #define HFS_VALID_MODE_BITS (S_IFREG | S_IFDIR | S_IRWXUGO)
static int hfs_writepage(struct page *page, struct writeback_control *wbc)
{
return block_write_full_page(page, hfs_get_block, wbc);
}
static int hfs_read_folio(struct file *file, struct folio *folio) static int hfs_read_folio(struct file *file, struct folio *folio)
{ {
return block_read_full_folio(folio, hfs_get_block); return block_read_full_folio(folio, hfs_get_block);
...@@ -162,9 +157,10 @@ const struct address_space_operations hfs_btree_aops = { ...@@ -162,9 +157,10 @@ const struct address_space_operations hfs_btree_aops = {
.dirty_folio = block_dirty_folio, .dirty_folio = block_dirty_folio,
.invalidate_folio = block_invalidate_folio, .invalidate_folio = block_invalidate_folio,
.read_folio = hfs_read_folio, .read_folio = hfs_read_folio,
.writepage = hfs_writepage, .writepages = hfs_writepages,
.write_begin = hfs_write_begin, .write_begin = hfs_write_begin,
.write_end = generic_write_end, .write_end = generic_write_end,
.migrate_folio = buffer_migrate_folio,
.bmap = hfs_bmap, .bmap = hfs_bmap,
.release_folio = hfs_release_folio, .release_folio = hfs_release_folio,
}; };
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment