From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Subject: [PATCH 0/6] xfs: accumulated fixes for 4.6
Date: Mon, 7 Mar 2016 08:49:44 +1100 [thread overview]
Message-ID: <1457300990-18300-1-git-send-email-david@fromorbit.com> (raw)
Hi folks,
This series is mostly fixes pulled from Darrick's rmap tree and one
for a growfs log recovery fix from me. I'm posting them mainly for a
final check before I merge them, and so everyone knows what is going
to be merged from Darrick's trees before the merge actually occurs.
Realistically, I'm not going to wait for days for people to
check/review these patch series before I merge them. If i don't hear
any objections within a couple of days, I'll simply push them out
into the for-next tree. Yes, I know this is a bit different to the
normal process, but I'm not posting these patches from Darrick's
tree until I've already reviewed (and therefore tested) them.
Cheers,
Dave.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2016-03-06 21:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-06 21:49 Dave Chinner [this message]
2016-03-06 21:49 ` [PATCH 1/6] xfs: reinitialise per-AG structures if geometry changes during recovery Dave Chinner
2016-03-07 16:24 ` Christoph Hellwig
2016-03-06 21:49 ` [PATCH 2/6] xfs: ioends require logically contiguous file offsets Dave Chinner
2016-03-07 16:26 ` Christoph Hellwig
2016-03-08 2:33 ` Darrick J. Wong
2016-03-08 7:01 ` Christoph Hellwig
2016-03-06 21:49 ` [PATCH 3/6] xfs: fix computation of inode btree maxlevels Dave Chinner
2016-03-06 21:49 ` [PATCH 4/6] xfs: use named array initializers for log item dumping Dave Chinner
2016-03-07 16:27 ` Christoph Hellwig
2016-03-06 21:49 ` [PATCH 5/6] xfs: check sizes of XFS on-disk structures at compile time Dave Chinner
2016-03-07 16:27 ` Christoph Hellwig
2016-03-06 21:49 ` [PATCH 6/6] xfs: pad xfs_attr_leaf_name_remote to avoid tripping on m68k Dave Chinner
2016-03-07 16:28 ` Christoph Hellwig
2016-03-08 3:56 ` Dave Chinner
2016-03-08 7:02 ` Christoph Hellwig
2016-03-08 17:34 ` Christoph Hellwig
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=1457300990-18300-1-git-send-email-david@fromorbit.com \
--to=david@fromorbit.com \
--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