From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: xfs <linux-xfs@vger.kernel.org>
Subject: Re: [ANNOUNCE] xfs-linux: for-next updated to 0cbf8c9
Date: Fri, 31 Mar 2017 09:04:38 -0700 [thread overview]
Message-ID: <20170331160438.GA3255@infradead.org> (raw)
In-Reply-To: <20170330173724.GE4864@birch.djwong.org>
On Thu, Mar 30, 2017 at 10:37:24AM -0700, Darrick J. Wong wrote:
> has just been updated. I intend to try to put in Eric Sandeen's patches
> to perform unlinked inode cleanup during ro mount and my own GETFSMAP
> patches for 4.12, so I put them in along with the other fixes and
> cleanups to get further testing.
Any chance we could not use for-next for stuff that's just queued up
for testing?
next prev parent reply other threads:[~2017-03-31 16:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-30 17:37 [ANNOUNCE] xfs-linux: for-next updated to 0cbf8c9 Darrick J. Wong
2017-03-31 16:04 ` Christoph Hellwig [this message]
2017-03-31 17:06 ` Darrick J. Wong
2017-04-02 0:02 ` Dave Chinner
2017-04-03 18:39 ` Darrick J. Wong
2017-04-03 18:56 ` Eric Sandeen
2017-04-04 11:20 ` Brian Foster
2017-04-04 18:15 ` Darrick J. Wong
2017-04-05 11:48 ` Brian Foster
2017-04-05 18:01 ` Darrick J. Wong
2017-04-04 12:50 ` Dave Chinner
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=20170331160438.GA3255@infradead.org \
--to=hch@infradead.org \
--cc=darrick.wong@oracle.com \
--cc=linux-xfs@vger.kernel.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).