From: Andreas Gruenbacher <agruenba@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 0/4] gfs2: Cleanups for next merge window
Date: Tue, 27 Jun 2017 18:50:39 +0200 [thread overview]
Message-ID: <1498582243-7385-1-git-send-email-agruenba@redhat.com> (raw)
Here are four cleanups I would like to see in the next merge window. The first
three have been posted here in previous versions before; the fourth is new.
Thanks,
Andreas
Andreas Gruenbacher (4):
gfs2: Get rid of flush_delayed_work in gfs2_evict_inode
gfs2: Protect gl->gl_object by spin lock
gfs2: Clean up glock work enqueuing
gfs2: gfs2_create_inode: Keep glock across iput
fs/gfs2/bmap.c | 2 +-
fs/gfs2/dir.c | 4 +-
fs/gfs2/glock.c | 124 +++++++++++++++++++++++++++++++++----------------------
fs/gfs2/glock.h | 7 ++++
fs/gfs2/glops.c | 56 ++++++++++++++++++++-----
fs/gfs2/incore.h | 3 ++
fs/gfs2/inode.c | 19 +++++----
fs/gfs2/lops.c | 2 +-
fs/gfs2/rgrp.c | 6 +--
fs/gfs2/super.c | 33 +++++++++------
fs/gfs2/xattr.c | 4 +-
11 files changed, 170 insertions(+), 90 deletions(-)
--
2.7.5
next reply other threads:[~2017-06-27 16:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-27 16:50 Andreas Gruenbacher [this message]
2017-06-27 16:50 ` [Cluster-devel] [PATCH 1/4] gfs2: Get rid of flush_delayed_work in gfs2_evict_inode Andreas Gruenbacher
2017-06-27 16:50 ` [Cluster-devel] [PATCH 2/4] gfs2: Protect gl->gl_object by spin lock Andreas Gruenbacher
2017-06-27 16:50 ` [Cluster-devel] [PATCH 3/4] gfs2: Clean up glock work enqueuing Andreas Gruenbacher
2017-06-27 16:50 ` [Cluster-devel] [PATCH 4/4] gfs2: gfs2_create_inode: Keep glock across iput Andreas Gruenbacher
2017-06-30 13:29 ` [Cluster-devel] [PATCH 0/4] gfs2: Cleanups for next merge window Bob Peterson
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=1498582243-7385-1-git-send-email-agruenba@redhat.com \
--to=agruenba@redhat.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;
as well as URLs for NNTP newsgroup(s).