From: Daniel DeFreez <dcdefreez@ucdavis.edu>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] GFS2: Always call gfs2_holder_uninit after gfs_holder_init?
Date: Fri, 15 Apr 2016 13:30:24 -0700 [thread overview]
Message-ID: <20160415203023.GA29608@ceres> (raw)
In-Reply-To: <229783496.51602257.1460730608253.JavaMail.zimbra@redhat.com>
Bob,
Thank you for the explanation. I will send a patch in a few minutes that
includes the other location that follows a similar path. I'm sending the patch
for the sake of practice, so disregard if it isn't helpful.
Daniel
prev parent reply other threads:[~2016-04-15 20:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 1:44 [Cluster-devel] GFS2: Always call gfs2_holder_uninit after gfs_holder_init? Daniel DeFreez
2016-04-15 14:30 ` Bob Peterson
2016-04-15 20:30 ` Daniel DeFreez [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=20160415203023.GA29608@ceres \
--to=dcdefreez@ucdavis.edu \
/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).