From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] GFS2 Patches Needing Review
Date: Thu, 8 Jun 2017 16:20:49 -0400 (EDT) [thread overview]
Message-ID: <1393838080.20623279.1496953249173.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1328319350.20617357.1496952538808.JavaMail.zimbra@redhat.com>
Hi,
Here is a list of recent GFS2 patches that I'd like reviewed before I push
them to the for-next branch:
Bob Peterson:
(1) https://www.redhat.com/archives/cluster-devel/2017-May/msg00116.html
26 May 2017 [GFS2 PATCH resend/revised] GFS2: Add new debug trace point and evict code path
(2) https://www.redhat.com/archives/cluster-devel/2017-May/msg00114.html
26 May 2017 [GFS2 PATCH V2] GFS2: Combine func meta_prep_new with its only caller
(3) https://www.redhat.com/archives/cluster-devel/2017-May/msg00115.html
26 May 2017 [GFS2 PATCH] GFS2: Withdraw when directory entry inconsistencies are detected
Andreas Gruenbacher:
(4) https://www.redhat.com/archives/cluster-devel/2017-May/msg00117.html
31 May 2017 [PATCH 0/8] GFS2 shrinker deadlock
(series of 8, revised)
Regards,
Bob Peterson
Red Hat File Systems
next parent reply other threads:[~2017-06-08 20:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1328319350.20617357.1496952538808.JavaMail.zimbra@redhat.com>
2017-06-08 20:20 ` Bob Peterson [this message]
2017-06-09 8:35 ` [Cluster-devel] GFS2 Patches Needing Review Steven Whitehouse
2017-06-09 14:13 ` 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=1393838080.20623279.1496953249173.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 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).