From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Subject: [ANNOUNCE] xfs: for-next branch rebased to aa49338
Date: Thu, 20 Aug 2015 09:40:49 +1000 [thread overview]
Message-ID: <20150819234049.GM3902@dastard> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 710 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 rebased to add a build fix to the
xfs-misc-fixes-for-4.3-2 topic branch. The new commits are below.
-Dave.
The new head of the for-next branch is commit:
aa49338 Merge branch 'xfs-misc-fixes-for-4.3-2' into for-next
New Commits:
Dave Chinner (2):
[3403ccc] xfs: inode lockdep annotations broke non-lockdep build
[aa49338] Merge branch 'xfs-misc-fixes-for-4.3-2' into for-next
Code Diffstat:
fs/xfs/xfs_inode.c | 16 ++++++++++++++--
1 file changed, 14 insertions(+), 2 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-19 23:41 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=20150819234049.GM3902@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