From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 0/5] gfs2: Various minor cleanups
Date: Mon, 4 Jun 2018 11:39:33 -0400 (EDT) [thread overview]
Message-ID: <734839428.39830516.1528126773243.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20180602095045.31469-1-agruenba@redhat.com>
----- Original Message -----
> I've been carrying these five patches as part of the iomap-write patch
> queue, but they should be good for gfs2's for-next branch by now.
> Please apply.
>
> Thanks,
> Andreas
>
> Andreas Gruenbacher (5):
> gfs2: Update find_metapath comment
> gfs2: hole_size improvement
> gfs2: gfs2_stuffed_write_end cleanup
> gfs2: Remove ordered write mode handling from gfs2_trans_add_data
> gfs2: Iomap cleanups and improvements
>
> fs/gfs2/aops.c | 56 +++----
> fs/gfs2/bmap.c | 416 +++++++++++++++++++++++++++++++-----------------
> fs/gfs2/bmap.h | 6 +-
> fs/gfs2/file.c | 6 +-
> fs/gfs2/inode.c | 4 -
> fs/gfs2/log.h | 7 +-
> fs/gfs2/quota.c | 5 +-
> fs/gfs2/trans.c | 27 +---
> 8 files changed, 321 insertions(+), 206 deletions(-)
>
> --
> 2.17.0
>
>
Hi,
Thanks. This patch set is now pushed to the for-next branch of the linux-gfs2 tree.
Regards,
Bob Peterson
Red Hat File Systems
prev parent reply other threads:[~2018-06-04 15:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-02 9:50 [Cluster-devel] [PATCH 0/5] gfs2: Various minor cleanups Andreas Gruenbacher
2018-06-02 9:50 ` [Cluster-devel] [PATCH 1/5] gfs2: Update find_metapath comment Andreas Gruenbacher
2018-06-02 9:50 ` [Cluster-devel] [PATCH 2/5] gfs2: hole_size improvement Andreas Gruenbacher
2018-06-02 9:50 ` [Cluster-devel] [PATCH 3/5] gfs2: gfs2_stuffed_write_end cleanup Andreas Gruenbacher
2018-06-02 9:50 ` [Cluster-devel] [PATCH 4/5] gfs2: Remove ordered write mode handling from gfs2_trans_add_data Andreas Gruenbacher
2018-06-02 9:50 ` [Cluster-devel] [PATCH 5/5] gfs2: Iomap cleanups and improvements Andreas Gruenbacher
2018-06-04 15:39 ` Bob Peterson [this message]
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=734839428.39830516.1528126773243.JavaMail.zimbra@redhat.com \
--to=rpeterso@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.