From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Subject: [ANNOUNCE] xfs: for-next branch updated to ab9d1e4
Date: Wed, 9 Mar 2016 08:28:47 +1100 [thread overview]
Message-ID: <20160308212847.GW30721@dastard> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1251 bytes --]
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.
The new head of the for-next branch is commit:
ab9d1e4 Merge branch 'xfs-misc-fixes-4.6-3' into for-next
New Commits:
Darrick J. Wong (3):
[49ca911] xfs: fix computation of inode btree maxlevels
[5110cd8] xfs: use named array initializers for log item dumping
[30cbc59] xfs: check sizes of XFS on-disk structures at compile time
Dave Chinner (2):
[a798011] xfs: reinitialise per-AG structures if geometry changes during recovery
[ab9d1e4] Merge branch 'xfs-misc-fixes-4.6-3' into for-next
Luis de Bethencourt (1):
[a5fd276] xfs: remove impossible condition
Code Diffstat:
fs/xfs/libxfs/xfs_bmap.c | 5 +-
fs/xfs/libxfs/xfs_ialloc.c | 4 +-
fs/xfs/xfs_log.c | 132 ++++++++++++++++++++++++-----------------------
fs/xfs/xfs_log_recover.c | 22 ++++----
fs/xfs/xfs_ondisk.h | 117 +++++++++++++++++++++++++++++++++++++++++
fs/xfs/xfs_super.c | 3 ++
6 files changed, 204 insertions(+), 79 deletions(-)
create mode 100644 fs/xfs/xfs_ondisk.h
--
Dave Chinner
david@fromorbit.com
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
reply other threads:[~2016-03-08 21:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20160308212847.GW30721@dastard \
--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