From: mbroz@sourceware.org <mbroz@sourceware.org>
To: lvm-devel@redhat.com
Subject: LVM2 ./WHATS_NEW lib/commands/toolcontext.c
Date: 14 Jul 2009 12:17:15 -0000 [thread overview]
Message-ID: <20090714121715.5020.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: mbroz at sourceware.org 2009-07-14 12:17:15
Modified files:
. : WHATS_NEW
lib/commands : toolcontext.c
Log message:
Enable use of new multi-segment registration for static registration too.
so it allows this use:
#ifdef MYNEWSEG_INTERNAL
if (!init_mynewseg_segtypes(&seglib))
return 0;
#endif
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.1182&r2=1.1183
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/lib/commands/toolcontext.c.diff?cvsroot=lvm2&r1=1.78&r2=1.79
--- LVM2/WHATS_NEW 2009/07/14 11:01:26 1.1182
+++ LVM2/WHATS_NEW 2009/07/14 12:17:14 1.1183
@@ -1,5 +1,6 @@
Version 2.02.49 -
================================
+ Enable use of new multi-segment registration for static registration too.
Exclude VG_GLOBAL from vg_write_lock_held so scans open devs read-only again.
Add unit test case for liblvm VG create/delete APIs.
Add liblvm APIs to implement creation and deletion of VGs.
--- LVM2/lib/commands/toolcontext.c 2009/07/08 18:12:08 1.78
+++ LVM2/lib/commands/toolcontext.c 2009/07/14 12:17:15 1.79
@@ -855,10 +855,10 @@
static int _init_segtypes(struct cmd_context *cmd)
{
struct segment_type *segtype;
+ struct segtype_library seglib = { .cmd = cmd };
#ifdef HAVE_LIBDL
const struct config_node *cn;
- struct segtype_library seglib;
#endif
if (!(segtype = init_striped_segtype(cmd)))
next reply other threads:[~2009-07-14 12:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-14 12:17 mbroz [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-05-23 13:02 LVM2 ./WHATS_NEW lib/commands/toolcontext.c zkabelac
2012-03-23 9:42 zkabelac
2012-02-27 10:05 zkabelac
2012-02-08 10:46 zkabelac
2011-07-08 16:49 agk
2011-06-28 0:23 agk
2010-11-24 9:34 zkabelac
2010-04-30 12:37 zkabelac
2009-07-21 20:00 mpatocka
2009-06-15 11:56 mbroz
2009-04-02 20:46 taka
2007-02-08 17:31 agk
2007-01-23 16:03 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=20090714121715.5020.qmail@sourceware.org \
--to=mbroz@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.