linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Ira Weiny <ira.weiny@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
	Josef Bacik <josef@toxicpanda.com>,
	Anna Schumaker <anna.schumaker@netapp.com>,
	linux-xfs@vger.kernel.org, Chris Mason <clm@fb.com>,
	David Sterba <dsterba@suse.com>, Jaegeuk Kim <jaegeuk@kernel.org>,
	linux-f2fs-devel@lists.sourceforge.net,
	Trond Myklebust <trond.myklebust@hammerspace.com>,
	linux-btrfs@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH V2 0/2] Move swap functions out of address space operations
Date: Thu, 14 Nov 2019 15:19:24 -0800	[thread overview]
Message-ID: <20191114231924.GA4370@iweiny-DESK2.sc.intel.com> (raw)
In-Reply-To: <20191113004244.9981-1-ira.weiny@intel.com>

On Tue, Nov 12, 2019 at 04:42:42PM -0800, 'Ira Weiny' wrote:
> From: Ira Weiny <ira.weiny@intel.com>
> 
> As suggested by Jan Kara, move swap_[de]activate to file_operations to simplify
> address space operations for coming changes.
> 
> I'm not sure if this should go through Al Viro or Andrew Morton so I'm sending
> it to both of you.  Sorry if this is a problem.  Let me know if there is
> something else I should do.
> 
> Ira Weiny (2):
>   fs: Clean up mapping variable
>   fs: Move swap_[de]activate to file_operations

There should have been an update to the documentation with this.

I have a 3rd patch which I'm sending separately.

Ira

> 
>  fs/btrfs/file.c     | 341 ++++++++++++++++++++++++++++++++++++++++++++
>  fs/btrfs/inode.c    | 340 -------------------------------------------
>  fs/f2fs/data.c      | 123 ----------------
>  fs/f2fs/file.c      | 122 ++++++++++++++++
>  fs/iomap/swapfile.c |   3 +-
>  fs/nfs/file.c       |   4 +-
>  fs/xfs/xfs_aops.c   |  13 --
>  fs/xfs/xfs_file.c   |  12 ++
>  include/linux/fs.h  |  10 +-
>  mm/swapfile.c       |  12 +-
>  10 files changed, 488 insertions(+), 492 deletions(-)
> 
> -- 
> 2.21.0
> 


_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

      parent reply	other threads:[~2019-11-14 23:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-13  0:42 [f2fs-dev] [PATCH V2 0/2] Move swap functions out of address space operations ira.weiny
2019-11-13  0:42 ` [f2fs-dev] [PATCH V2 1/2] fs: Clean up mapping variable ira.weiny
2019-11-14 21:02   ` Darrick J. Wong
2019-11-13  0:42 ` [f2fs-dev] [PATCH V2 2/2] fs: Move swap_[de]activate to file_operations ira.weiny
2019-11-13  0:57   ` Darrick J. Wong
2019-11-13 15:25   ` David Sterba
2019-11-14 21:03   ` Darrick J. Wong
2019-11-19 18:57     ` Ira Weiny
2019-11-14 23:19 ` Ira Weiny [this message]

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=20191114231924.GA4370@iweiny-DESK2.sc.intel.com \
    --to=ira.weiny@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=anna.schumaker@netapp.com \
    --cc=clm@fb.com \
    --cc=dsterba@suse.com \
    --cc=jaegeuk@kernel.org \
    --cc=josef@toxicpanda.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=trond.myklebust@hammerspace.com \
    /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).