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 5d54b8c
Date: Tue, 1 Sep 2015 10:53:26 +1000	[thread overview]
Message-ID: <20150901005326.GP3902@dastard> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1220 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. This is the final update that will occur for
the 4.3 merge window. Once this has sat in linux-next for a couple
of days (assuming no problems arise) I'll tag it and send a pull
request to Linus....

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

5d54b8c Merge branch 'xfs-misc-fixes-for-4.3-4' into for-next

New Commits:

Darrick J. Wong (1):
      [dfdd4ac] libxfs: bad magic number should set da block buffer error

Dave Chinner (1):
      [5d54b8c] Merge branch 'xfs-misc-fixes-for-4.3-4' into for-next

David Jeffery (1):
      [c9eb256] xfs: return errors from partial I/O failures to files

Eric Sandeen (1):
      [1a7ccad] xfs: fix error gotos in xfs_setattr_nonsize

Lucas Stach (1):
      [8774cf8] xfs: add mssing inode cache attempts counter increment


Code Diffstat:

 fs/xfs/libxfs/xfs_da_btree.c | 1 +
 fs/xfs/xfs_aops.c            | 3 ++-
 fs/xfs/xfs_icache.c          | 2 ++
 fs/xfs/xfs_iops.c            | 8 ++++----
 4 files changed, 9 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-09-01  1:08 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=20150901005326.GP3902@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