From: Christoph Hellwig <hch@lst.de>
To: Jens Axboe <axboe@fb.com>
Cc: David Howells <dhowells@redhat.com>,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
linux-mtd@lists.infradead.org
Subject: backing_dev_info cleanups
Date: Tue, 30 Dec 2014 09:57:31 +0100 [thread overview]
Message-ID: <1419929859-24427-1-git-send-email-hch@lst.de> (raw)
This series cleans up how we use the backing_dev_info structure in
preparation for fixing the life time rules for it. The most important
change is to split the unrelated nommu mmap flags from it, but it
also remove a backing_dev_info pointer from the address_space
(and thus the inode) and cleans up various other minor bits.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2014-12-30 8:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-30 8:57 Christoph Hellwig [this message]
2014-12-30 8:57 ` [PATCH 1/8] fs: deduplicate noop_backing_dev_info Christoph Hellwig
2014-12-30 8:57 ` [PATCH 2/8] fs: kill BDI_CAP_SWAP_BACKED Christoph Hellwig
2014-12-30 8:57 ` [PATCH 3/8] fs: introduce f_op->mmap_capabilities for nommu mmap support Christoph Hellwig
2014-12-30 8:57 ` [PATCH 4/8] block_dev: only write bdev inode on close Christoph Hellwig
2014-12-30 8:57 ` [PATCH 5/8] block_dev: get bdev inode bdi directly from the block device Christoph Hellwig
2014-12-30 8:57 ` [PATCH 6/8] nilfs2: set up s_bdi like the generic mount_bdev code Christoph Hellwig
2015-01-04 8:18 ` Ryusuke Konishi
2014-12-30 8:57 ` [PATCH 7/8] fs: export inode_to_bdi and use it in favor of mapping->backing_dev_info Christoph Hellwig
2014-12-30 8:57 ` [PATCH 8/8] fs: remove mapping->backing_dev_info Christoph Hellwig
2015-01-04 8:28 ` Ryusuke Konishi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1419929859-24427-1-git-send-email-hch@lst.de \
--to=hch@lst.de \
--cc=axboe@fb.com \
--cc=dhowells@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-mtd@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).