All of lore.kernel.org
 help / color / mirror / Atom feed
From: wysochanski@sourceware.org <wysochanski@sourceware.org>
To: lvm-devel@redhat.com
Subject: LVM2 ./WHATS_NEW lib/device/dev-md.c
Date: 23 Jun 2008 19:26:21 -0000	[thread overview]
Message-ID: <20080623192621.22111.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/lvm2
Module name:	LVM2
Changes by:	wysochanski at sourceware.org	2008-06-23 19:26:21

Modified files:
	.              : WHATS_NEW 
	lib/device     : dev-md.c 

Log message:
	Suppress invalid 'sb_offset' compiler warning (FC8) with uninitialized_var().
	
	device/dev-md.c:61: warning: ???sb_offset??? may be used uninitialized in this function

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.913&r2=1.914
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/lib/device/dev-md.c.diff?cvsroot=lvm2&r1=1.9&r2=1.10

--- LVM2/WHATS_NEW	2008/06/23 19:04:34	1.913
+++ LVM2/WHATS_NEW	2008/06/23 19:26:20	1.914
@@ -1,5 +1,6 @@
 Version 2.02.39 -
 ================================
+  Suppress invalid 'sb_offset' compiler warning with uninitialzed_var().
   Add uninitialzed_var() macro to suppress invalid compiler warnings.
   Suppress 'sb_offset' compiler warning by using enum for md minor sb version. 
   lvm2_run: Don't return uninitialized "ret" for _memlock_inc or _memlock_dec.
--- LVM2/lib/device/dev-md.c	2008/06/23 14:54:50	1.9
+++ LVM2/lib/device/dev-md.c	2008/06/23 19:26:21	1.10
@@ -58,7 +58,7 @@
 
 static uint64_t _v1_sb_offset(uint64_t size, md_minor_version_t minor_version)
 {
-	uint64_t sb_offset;
+	uint64_t uninitialized_var(sb_offset);
 
 	switch(minor_version) {
 	case MD_MINOR_V0:



             reply	other threads:[~2008-06-23 19:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-23 19:26 wysochanski [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-07-08 15:54 LVM2 ./WHATS_NEW lib/device/dev-md.c mbroz
2008-06-23 14:54 wysochanski
2007-10-24  0:51 agk
2007-01-26 17:15 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=20080623192621.22111.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.