All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zdenek Kabelac <zkabelac@redhat.com>
To: lvm-devel@redhat.com
Subject: [PATCH 3/4] Add lvm_lvseg_get_property() function.
Date: Wed, 20 Oct 2010 13:47:28 +0200	[thread overview]
Message-ID: <4CBED6D0.9040809@redhat.com> (raw)
In-Reply-To: <1287494696-18310-4-git-send-email-dwysocha@redhat.com>

Dne 19.10.2010 15:24, Dave Wysochanski napsal(a):
> 
> Signed-off-by: Dave Wysochanski <dwysocha@redhat.com>
> ---
> 
> diff --git a/liblvm/lvm2app.h b/liblvm/lvm2app.h
> index f6d54f1..7e2eb69 100644
> --- a/liblvm/lvm2app.h
> +++ b/liblvm/lvm2app.h
> @@ -1099,6 +1099,45 @@ uint64_t lvm_lv_get_size(const lv_t lv);
>  struct lvm_property_value lvm_lv_get_property(const lv_t lv, const char *name);
>  
>  /**
> + * Get the value of a LV segment property
> + *
> + * \memberof lv_t
> + *
> + * \param   lvseg
> + * Logical volume segment handle.
> + *
> + * \param   name
> + * Name of property to query.  See lvs man page for full list of properties
> + * that may be queried.
> + *
> + * The memory allocated for a string property value is tied to the vg_t
> + * handle and will be released when lvm_vg_close() is called.
> + *
> + * Example:
> + *      lvm_property_value v;
> + *      char *prop_name = "seg_start_pe";
> + *
> + *      v = lvm_lvseg_get_property(lv, prop_name);
> + *      if (lvm_errno(libh) || !v.is_valid) {
> + *           // handle error
> + *           printf("Invalid property name or unable to query"
> + *                  "'%s'.\n", prop_name);
> + *           return;
> + *      }

That's IMHO not practical.

if (!lvm_lvseg_get_property(lv, prop_name, &v)) {
	/* error  path */
}

or whatever return error status we use, looks much more natural.


Zdenek



  reply	other threads:[~2010-10-20 11:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-19 13:24 [PATCH 00/04] Add lvm lvseg properties for lvm2app Dave Wysochanski
2010-10-19 13:24 ` [PATCH 1/4] Add lvseg_t to lvm2app and lvm_lv_list_lvsegs() Dave Wysochanski
2010-10-19 13:24 ` [PATCH 2/4] Add lvseg 'get' functions Dave Wysochanski
2010-10-20 11:53   ` Zdenek Kabelac
2010-10-21 16:36     ` Petr Rockai
2010-10-19 13:24 ` [PATCH 3/4] Add lvm_lvseg_get_property() function Dave Wysochanski
2010-10-20 11:47   ` Zdenek Kabelac [this message]
2010-10-19 13:24 ` [PATCH 4/4] Update tests for lvseg apis Dave Wysochanski
2010-10-20 12:08   ` Zdenek Kabelac
2010-10-21 16:38     ` Petr Rockai
2010-10-22  8:26       ` Zdenek Kabelac
2010-10-22  8:59         ` Petr Rockai
2010-10-24 16:24           ` Zdenek Kabelac
2010-10-24 21:06             ` Petr Rockai
2010-10-25 13:27               ` Zdenek Kabelac

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=4CBED6D0.9040809@redhat.com \
    --to=zkabelac@redhat.com \
    --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.