linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-xfs@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: [ANNOUNCE] xfs: for-next branch updated to 800b269
Date: Fri, 26 Aug 2016 00:48:44 -0700	[thread overview]
Message-ID: <20160826074844.GA17137@infradead.org> (raw)
In-Reply-To: <20160826062508.GG19025@dastard>

Hi Dave,

please consider: "[PATCH] iomap: don't set FIEMAP_EXTENT_MERGED for
extent based filesystems"

for 4.8.  It fixes a regression in the iomap-based fiemap
implementation, and it's fairly trivial as well.

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2016-08-26  7:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-26  6:25 [ANNOUNCE] xfs: for-next branch updated to 800b269 Dave Chinner
2016-08-26  7:48 ` Christoph Hellwig [this message]
2016-08-29  1:31   ` Dave Chinner
2016-08-29 14:52     ` Darrick J. Wong
2016-08-29 23:23       ` Dave Chinner
2016-08-30  3:40         ` Darrick J. Wong

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=20160826074844.GA17137@infradead.org \
    --to=hch@infradead.org \
    --cc=david@fromorbit.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=xfs@oss.sgi.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).