linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Clements <paul.clements@steeleye.com>
To: Neil Brown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: ANNOUNCE: mdadm 2.5.1 - A tool for managing Soft RAID under Linux
Date: Fri, 16 Jun 2006 11:46:51 -0400	[thread overview]
Message-ID: <4492D26B.4070705@steeleye.com> (raw)
In-Reply-To: <17554.895.666628.776527@cse.unsw.edu.au>

[-- Attachment #1: Type: text/plain, Size: 402 bytes --]

Neil Brown wrote:
> 
> I am pleased to announce the availability of
>    mdadm version 2.5.1

Hi Neil,

Here's a small patch to allow compilation on gcc 2.x. It looks like gcc 
3.x allows variable declarations that are not at the start of a block of 
code (I don't know if there's some standard that allows that in C code 
now, but it doesn't work with all C compilers).

Patch attached.

Thanks,
Paul

[-- Attachment #2: mdadm-2.5.1-super1-compile-error.diff --]
[-- Type: text/plain, Size: 563 bytes --]

--- mdadm-2.5.1/super1.c.orig	Fri Jun 16 11:27:16 2006
+++ mdadm-2.5.1/super1.c	Fri Jun 16 11:28:20 2006
@@ -309,6 +309,7 @@ static void brief_examine_super1(void *s
 	struct mdp_superblock_1 *sb = sbv;
 	int i;
 	char *nm;
+	char *c=map_num(pers, __le32_to_cpu(sb->level));
 
 	nm = strchr(sb->set_name, ':');
 	if (nm)
@@ -317,8 +318,6 @@ static void brief_examine_super1(void *s
 		nm = sb->set_name;
 	else
 		nm = "??";
-
-	char *c=map_num(pers, __le32_to_cpu(sb->level));
 
 	printf("ARRAY /dev/md/%s level=%s metadata=1 num-devices=%d UUID=",
 	       nm,

  reply	other threads:[~2006-06-16 15:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-16  1:03 ANNOUNCE: mdadm 2.5.1 - A tool for managing Soft RAID under Linux Neil Brown
2006-06-16 15:46 ` Paul Clements [this message]
2006-06-16 17:54   ` Bill Davidsen
2006-06-19 15:09     ` [PATCH] " Paul Clements
2006-06-19 18:58       ` Paul Clements
2006-06-20  0:04         ` Neil Brown
2006-06-19 19:02       ` Paul Clements
2006-06-17  2:12 ` mdadm 2.5.1 - A problem came up Mr. James W. Laferriere
2006-06-17  7:00   ` Neil Brown

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=4492D26B.4070705@steeleye.com \
    --to=paul.clements@steeleye.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    /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 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 NNTP newsgroup(s).