public inbox for lvm2-cvs@sourceware.org help / color / mirror / Atom feed
From: zkabelac@sourceware.org To: lvm-devel@redhat.com, lvm2-cvs@sourceware.org Subject: LVM2 ./WHATS_NEW_DM tools/dmsetup.c Date: Tue, 29 Mar 2011 21:49:00 -0000 [thread overview] Message-ID: <20110329214919.19743.qmail@sourceware.org> (raw) CVSROOT: /cvs/lvm2 Module name: LVM2 Changes by: zkabelac@sourceware.org 2011-03-29 21:49:18 Modified files: . : WHATS_NEW_DM tools : dmsetup.c Log message: Const warning fixes With recent update of dm_report_field_string() API call to accept completely const objects - we no longer need loose constness here and keep it forwarding. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW_DM.diff?cvsroot=lvm2&r1=1.458&r2=1.459 http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/tools/dmsetup.c.diff?cvsroot=lvm2&r1=1.156&r2=1.157 --- LVM2/WHATS_NEW_DM 2011/03/25 23:50:35 1.458 +++ LVM2/WHATS_NEW_DM 2011/03/29 21:49:18 1.459 @@ -1,5 +1,6 @@ Version 1.02.64 - =================================== + Fix const cast in dmsetup calls of dm_report_field_string(). Streamline /dev/mapper/control node code for common cases. Use hard-coded dm control node device number for 2.6.36 kernels and above. Improve stack debug reporting in dm_task_create(). --- LVM2/tools/dmsetup.c 2011/03/02 02:44:56 1.156 +++ LVM2/tools/dmsetup.c 2011/03/29 21:49:18 1.157 @@ -2455,7 +2455,7 @@ struct dm_report_field *field, const void *data, void *private __attribute__((unused))) { - return dm_report_field_string(rh, field, (const char **) data); + return dm_report_field_string(rh, field, (const char *const *) data); } static int _dm_vg_name_disp(struct dm_report *rh, @@ -2464,7 +2464,7 @@ void *private __attribute__((unused))) { - return dm_report_field_string(rh, field, (const char **) data); + return dm_report_field_string(rh, field, (const char *const *) data); } static int _dm_lv_name_disp(struct dm_report *rh, @@ -2473,7 +2473,7 @@ void *private __attribute__((unused))) { - return dm_report_field_string(rh, field, (const char **) data); + return dm_report_field_string(rh, field, (const char *const *) data); } static int _dm_lv_layer_name_disp(struct dm_report *rh, @@ -2482,7 +2482,7 @@ void *private __attribute__((unused))) { - return dm_report_field_string(rh, field, (const char **) data); + return dm_report_field_string(rh, field, (const char *const *) data); } static void *_task_get_obj(void *obj)
next reply other threads:[~2011-03-29 21:49 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-03-29 21:49 zkabelac [this message] -- strict thread matches above, loose matches on Subject: below -- 2012-04-24 8:24 prajnoha 2012-04-24 8:00 prajnoha 2012-03-01 21:56 zkabelac 2012-02-15 12:08 prajnoha 2012-02-15 12:06 prajnoha 2012-02-15 12:03 prajnoha 2012-02-13 12:06 zkabelac 2011-08-11 17:06 mbroz 2011-07-08 17:08 agk 2011-06-17 14:55 prajnoha 2011-03-02 2:44 agk 2010-08-03 13:04 zkabelac 2010-08-03 12:56 zkabelac 2010-07-08 14:29 zkabelac 2009-06-03 20:44 agk 2009-06-03 18:35 agk 2009-04-24 11:30 prajnoha
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=20110329214919.19743.qmail@sourceware.org \ --to=zkabelac@sourceware.org \ --cc=lvm-devel@redhat.com \ --cc=lvm2-cvs@sourceware.org \ /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: linkBe 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 read-only IMAP folder(s) and NNTP newsgroup(s).