From: "Jan Pokorný" <jpokorny@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 0/2] rgmanager: spots in flattening-related parts
Date: Mon, 2 Apr 2012 11:59:34 +0200 [thread overview]
Message-ID: <20120402095934.GA18543@redhat.com> (raw)
Just two spots I discovered while running through the code for flattening
resource trees in cluster.conf. One cosmetic, one little more subtle.
Jan Pokorn? (2):
resrules: fix free while passing the pointer to caller
resrules: print_resource_rule doc comment conformance
resrules.c | 9 +++------
1 files changed, 3 insertions(+), 6 deletions(-)
next reply other threads:[~2012-04-02 9:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-02 9:59 Jan Pokorný [this message]
2012-04-02 10:06 ` [Cluster-devel] [PATCH 1/2] resrules: fix free while passing the pointer to caller Jan Pokorný
2012-04-02 11:29 ` [Cluster-devel] [PATCH 1b/2] " Jan Pokorný
2012-04-02 15:46 ` Jan Pokorný
2012-04-02 10:08 ` [Cluster-devel] [PATCH 2/2] resrules: print_resource_rule doc comment conformance Jan Pokorný
2012-04-02 10:24 ` [Cluster-devel] [PATCH 2b/2] " Jan Pokorný
2012-04-02 11:37 ` [Cluster-devel] [PATCH 2c/2] " Jan Pokorný
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=20120402095934.GA18543@redhat.com \
--to=jpokorny@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).