From: Dave Chinner <david@fromorbit.com>
To: Eryu Guan <eguan@redhat.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [ANNOUNCE] xfs: for-next branch updated to a444d72e6090
Date: Fri, 9 Dec 2016 09:57:03 +1100 [thread overview]
Message-ID: <20161208225703.GK4219@dastard> (raw)
In-Reply-To: <20161208033250.GD29149@eguan.usersys.redhat.com>
On Thu, Dec 08, 2016 at 11:32:50AM +0800, Eryu Guan wrote:
> Hi Dave,
>
> On Thu, Dec 08, 2016 at 07:25:01AM +1100, Dave Chinner wrote:
> > Hi folks,
> >
> > The for-next branch of the xfs kernel repository at
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/dgc/linux-xfs.git
> >
> > has just been updated. This update contains a bunch of verification
> > enhancments to detect field corruptions as metadata is read from
> > disk, faster CRC calculations, a faster buffer cache indexing
> > structure and some cleanups.
> >
> > With the merge window likely to open next week, this may be the last
> > update for the 4.10-rc1 cycle. Let me know if there's anything
> > critical that I've missed for 4.10 so I can sort it out before the
> > end of the week.
>
> I didn't see patch "xfs: use xfs_vn_setattr_size to check on new size"
> was included in this update nor folded into other commits, do you want
> to take it for 4.10?
>
> http://www.spinics.net/lists/linux-xfs/msg02529.html
Ok, I missed that one - I did intend to pick it up. Will fix.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2016-12-08 22:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-07 20:25 [ANNOUNCE] xfs: for-next branch updated to a444d72e6090 Dave Chinner
2016-12-08 3:32 ` Eryu Guan
2016-12-08 22:57 ` Dave Chinner [this message]
2016-12-08 6:36 ` Darrick J. Wong
2016-12-08 22:58 ` 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=20161208225703.GK4219@dastard \
--to=david@fromorbit.com \
--cc=eguan@redhat.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