From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Subject: [PATCH 0/3, V2] xfs; fixes for 3.16-rc5
Date: Mon, 14 Jul 2014 14:48:56 +1000 [thread overview]
Message-ID: <1405313339-29110-1-git-send-email-david@fromorbit.com> (raw)
Hi folks,
This is an updated series of fixes for 3.16-rc5, first posted here:
http://oss.sgi.com/pipermail/xfs/2014-July/037159.html
The first patch is unchanged, the other two have been modified as a
result of review feedback (thanks Brian and Arkadiusz!).
Please review and test.
-Dave.
Version 2
- get rid of unused flags in struct xfs_bmalloca
- get rid of XFS_BMAPI_STACK_SWITCH
- fix gquotino being NULLed incorrectly when group quota was enabled
on filesystems with a shared group/project quota inode.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2014-07-14 4:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-14 4:48 Dave Chinner [this message]
2014-07-14 4:48 ` [PATCH 1/3] Revert "xfs: block allocation work needs to be kswapd aware" Dave Chinner
2014-07-14 4:48 ` [PATCH 2/3] xfs: refine the allocation stack switch Dave Chinner
2014-07-14 12:02 ` Brian Foster
2014-07-14 4:48 ` [PATCH 3/3] xfs: null unused quota inodes when quota is on Dave Chinner
2014-07-14 12:02 ` Brian Foster
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=1405313339-29110-1-git-send-email-david@fromorbit.com \
--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