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@xxxxxxxxxxxxx
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
