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 4e14e49
Date: Tue, 10 Nov 2015 11:16:00 +1100	[thread overview]
Message-ID: <20151110001600.GC14311@dastard> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1038 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. it contains the couple of outstanding fixes
for the 4.4 merge window. This is essentially what I'll ask linus to
pull in the next couple of days.

-Dave.

The new head of the for-next branch is commit:

4e14e49 Merge branch 'xfs-misc-fixes-for-4.4-3' into for-next

New Commits:

Andreas Gruenbacher (1):
      [edfb8eb] xfs: Fix error path in xfs_get_acl

Brian Foster (1):
      [848ccfc] xfs: fix log recovery op header validation assert

Chris Mason (1):
      [7a29ac4] xfs: give all workqueues rescuer threads

Dave Chinner (1):
      [4e14e49] Merge branch 'xfs-misc-fixes-for-4.4-3' into for-next


Code Diffstat:

 fs/xfs/xfs_acl.c         | 1 +
 fs/xfs/xfs_acl.h         | 1 -
 fs/xfs/xfs_log_recover.c | 2 +-
 fs/xfs/xfs_super.c       | 7 ++++---
 4 files changed, 6 insertions(+), 5 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-11-10  0:16 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=20151110001600.GC14311@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