From: wysochanski@sourceware.org <wysochanski@sourceware.org>
To: lvm-devel@redhat.com
Subject: LVM2 ./WHATS_NEW liblvm/lvm2app.h
Date: 12 Jul 2010 18:12:25 -0000 [thread overview]
Message-ID: <20100712181225.17641.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: wysochanski at sourceware.org 2010-07-12 18:12:24
Modified files:
. : WHATS_NEW
liblvm : lvm2app.h
Log message:
Update comments about memory handling in lvm2app.h.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.1664&r2=1.1665
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/liblvm/lvm2app.h.diff?cvsroot=lvm2&r1=1.17&r2=1.18
--- LVM2/WHATS_NEW 2010/07/12 11:37:49 1.1664
+++ LVM2/WHATS_NEW 2010/07/12 18:12:23 1.1665
@@ -1,5 +1,6 @@
Version 2.02.71 -
===============================
+ Update comments about memory handling in lvm2app.h.
Add more verbose messages while checking volume_list and hosttags settings.
Add log_error when strdup fails in {vg|lv}_change_tag().
Remove unnecessary includes in liblvm files.
--- LVM2/liblvm/lvm2app.h 2010/06/16 13:01:25 1.17
+++ LVM2/liblvm/lvm2app.h 2010/07/12 18:12:23 1.18
@@ -929,8 +929,8 @@
*
* \memberof lv_t
*
- * Memory is allocated using dm_malloc() and caller must free the memory
- * using dm_free().
+ * The memory allocated for the uuid is tied to the vg_t handle and will be
+ * released when lvm_vg_close() is called.
*
* \param lv
* Logical volume handle.
@@ -945,8 +945,8 @@
*
* \memberof lv_t
*
- * Memory is allocated using dm_malloc() and caller must free the memory
- * using dm_free().
+ * The memory allocated for the uuid is tied to the vg_t handle and will be
+ * released when lvm_vg_close() is called.
*
* \param lv
* Logical volume handle.
next reply other threads:[~2010-07-12 18:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-12 18:12 wysochanski [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-08-02 12:23 LVM2 ./WHATS_NEW liblvm/lvm2app.h agk
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=20100712181225.17641.qmail@sourceware.org \
--to=wysochanski@sourceware.org \
--cc=lvm-devel@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.