From: Dave Chinner <david@fromorbit.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
jack@suse.cz, tytso@mit.edu, ross.zwisler@linux.intel.com
Subject: Re: [ANNOUNCE] xfs: for-next branch updated to 84716639acc3
Date: Wed, 9 Nov 2016 12:23:43 +1100 [thread overview]
Message-ID: <20161109012343.GE28922@dastard> (raw)
In-Reply-To: <20161109000152.GB16813@birch.djwong.org>
On Tue, Nov 08, 2016 at 04:01:53PM -0800, Darrick J. Wong wrote:
> On Wed, Nov 09, 2016 at 10:16:39AM +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 includes the DAX iomap PMD fault infrastructure, a bunch
> > of libxfs cleanups that sync the kernel code with changes that
> > have been made in the userspace libxfs and a few bug fixes thrown in
> > there for good measure.
>
> /me notices the commit message for 132f2ac5055a96 ("xfs: check minimum block
> size for CRC filesystems") says that you cleaned up the XFS_MIN_CRC_BLOCKSIZE
> check, but the patch appears identical to the one that I sent. I think all
> you changed was removing the unlikely()...?
>
> (<shrug> I doubt it's a big deal either way really...)
Ok, that's a little strange.
Hmmm - looks like I hadn't saved the modified file when I refreshed
the patch after modifying the commit message. I've already updated
my local for-next tree, so when I next push it out it will have this
update in it.
/me accidentally demonstrates why he uses topic branches to isolate
different bodies of work and the reasons that for-next needs to be
considered an unstable branch...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2016-11-09 1:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-08 23:16 [ANNOUNCE] xfs: for-next branch updated to 84716639acc3 Dave Chinner
2016-11-09 0:01 ` Darrick J. Wong
2016-11-09 1:23 ` Dave Chinner [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=20161109012343.GE28922@dastard \
--to=david@fromorbit.com \
--cc=darrick.wong@oracle.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=ross.zwisler@linux.intel.com \
--cc=tytso@mit.edu \
/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).