All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Fabian Frederick <fabf@skynet.be>
Cc: linux-kernel@vger.kernel.org, osd-dev@open-osd.org,
	linux-ext4@vger.kernel.org, linux-nilfs@vger.kernel.org
Subject: Re: [PATCH 0/9 linux-next] move dir_pages() to pagemap.h
Date: Fri, 5 Jun 2015 15:43:44 +0100	[thread overview]
Message-ID: <20150605144344.GU7232@ZenIV.linux.org.uk> (raw)
In-Reply-To: <1432480791-31396-1-git-send-email-fabf@skynet.be>

On Sun, May 24, 2015 at 05:19:40PM +0200, Fabian Frederick wrote:
> This small patchset declares dir_pages() in pagemap.h and
> removes declarations in each filesystems.

Applied, with #2 and #4--9 folded into #1 - otherwise you get build breakage.

      parent reply	other threads:[~2015-06-05 14:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-24 15:19 [PATCH 0/9 linux-next] move dir_pages() to pagemap.h Fabian Frederick
2015-05-24 15:19 ` [PATCH 1/9 linux-next] pagemap.h: declare dir_pages() Fabian Frederick
2015-05-24 15:19 ` [PATCH 2/9 linux-next] nilfs2: remove dir_pages() declaration Fabian Frederick
     [not found]   ` <1432480791-31396-3-git-send-email-fabf-AgBVmzD5pcezQB+pC5nmwQ@public.gmane.org>
2015-05-25  1:06     ` Ryusuke Konishi
2015-05-25  1:06       ` Ryusuke Konishi
2015-05-24 15:19 ` [PATCH 3/9 linux-next] ufs: use dir_pages instead of ufs_dir_pages() Fabian Frederick
2015-05-24 15:19 ` [PATCH 4/9 linux-next] fs/qnx6: remove dir_pages() declaration Fabian Frederick
2015-05-24 15:19 ` [PATCH 5/9 linux-next] ext2: " Fabian Frederick
2015-05-24 15:19 ` [PATCH 6/9 linux-next] minix: " Fabian Frederick
2015-05-24 15:19 ` [PATCH 7/9 linux-next] exofs: " Fabian Frederick
2015-05-24 15:19 ` [PATCH 8/9 linux-next] sysv: " Fabian Frederick
2015-06-05 14:43 ` Al Viro [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=20150605144344.GU7232@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=fabf@skynet.be \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nilfs@vger.kernel.org \
    --cc=osd-dev@open-osd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.