public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Subject: [ANNOUNCE] xfs: for-next branch updated to 70b33a7
Date: Tue, 25 Aug 2015 13:37:08 +1000	[thread overview]
Message-ID: <20150825033708.GF714@dastard> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1222 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:

70b33a7 Merge branch 'xfs-misc-fixes-for-4.3-3' into for-next

New Commits:

Dave Chinner (3):
      [b6a9947] xfs: lockdep annotations throw warnings on non-debug builds
      [f79af0b] xfs: fix non-debug build warnings
      [70b33a7] Merge branch 'xfs-misc-fixes-for-4.3-3' into for-next

Eric Sandeen (1):
      [2ccf4a9] xfs: collapse allocsize and biosize mount option handling

Jan Kara (2):
      [c184f85] xfs: Fix uninitialized return value in xfs_alloc_fix_freelist()
      [0375423] xfs: Fix file type directory corruption for btree directories


Code Diffstat:

 fs/xfs/libxfs/xfs_alloc.c     |  2 +-
 fs/xfs/libxfs/xfs_dir2_node.c | 10 +++++++++-
 fs/xfs/xfs_buf.c              |  4 +---
 fs/xfs/xfs_buf_item.c         | 20 +++++++++++++-------
 fs/xfs/xfs_buf_item.h         |  2 +-
 fs/xfs/xfs_inode.c            |  8 +++++++-
 fs/xfs/xfs_super.c            | 12 ++----------
 7 files changed, 34 insertions(+), 24 deletions(-)
-- 
Dave Chinner
david@fromorbit.com

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 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:[~2015-08-25  3:37 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=20150825033708.GF714@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