From: NeilBrown <neilb@suse.de>
To: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>
Cc: Bernd Schubert <bernd.schubert@itwm.fraunhofer.de>,
linux-raid@vger.kernel.org
Subject: Re: [PATCH 0/6] raid6check fixes
Date: Mon, 24 Jun 2013 17:04:58 +1000 [thread overview]
Message-ID: <20130624170458.568dafcb@notabene.brown> (raw)
In-Reply-To: <20130620161639.GA3033@lazy.lzy>
[-- Attachment #1: Type: text/plain, Size: 1465 bytes --]
On Thu, 20 Jun 2013 18:16:39 +0200 Piergiorgio Sartor
<piergiorgio.sartor@nexgo.de> wrote:
> On Wed, Jun 19, 2013 at 10:08:03AM +1000, NeilBrown wrote:
> > On Tue, 18 Jun 2013 11:09:10 +0200 Bernd Schubert
> > <bernd.schubert@itwm.fraunhofer.de> wrote:
> >
> > > Here are a few raid6check fixes. This series also includes a patch for
> > > Makefile to allow to build with optimizations. I only fixed raid6check
> > > to build with -O3, but I don't have time left today to fix mdadm
> > > (e.g. Grow.c:2237:41: error: ‘info2.data_offset’ may be used uninitialized in this function [-Werror=uninitialized])
> > >
> >
> > Thanks for mentioning that. I've fix that problem.
> >
> > NeilBrown
> >
> >
> > > I wanted to send the memleak-fixes much earlier, but then
> > > I had been too busy. This patch is lightly tested, patches
> > > from today are only build-tested.
> >
>
> Hi Neil,
>
> BTW, what's your plan of including "raid6check"
> into a main release of "mdadm" package?
>
> Do you have "deadline" in mind?
What exactly do you mean by that?
raid6check.c is already in the upstream git tree and was in mdadm-3.2.5.
Do you mean when will it be included by distros? That is really up to them.
I could get "make install" to install it I guess.
I haven't really thought about what would be required for that.
I'll add it to my list of things to think about.
NeilBrown
>
> Thanks,
>
> bye,
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2013-06-24 7:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-18 9:09 [PATCH 0/6] raid6check fixes Bernd Schubert
2013-06-18 9:09 ` [PATCH 1/6] raid6check: Fix build of raid6check Bernd Schubert
2013-06-18 9:09 ` [PATCH 2/6] Makefile: Allow the user to pass EXTRA_CFLAGS Bernd Schubert
2013-06-19 0:07 ` NeilBrown
2013-06-19 9:48 ` Bernd Schubert
2013-06-24 7:01 ` NeilBrown
2013-06-18 9:09 ` [PATCH 3/6] raid6check: Fix memory leaks detected by valgrind Bernd Schubert
2013-06-18 9:09 ` [PATCH 4/6] raid6check: Use enums for repair type Bernd Schubert
2013-06-18 9:09 ` [PATCH 5/6] raid6check: Fix compiler warnings Bernd Schubert
2013-06-18 9:09 ` [PATCH 6/6] raid6check: Check return value of lseek64() Bernd Schubert
2013-06-18 17:16 ` [PATCH 0/6] raid6check fixes Piergiorgio Sartor
2013-06-19 0:08 ` NeilBrown
2013-06-20 16:16 ` Piergiorgio Sartor
2013-06-24 7:04 ` NeilBrown [this message]
2013-06-24 17:10 ` Piergiorgio Sartor
2013-06-24 23:54 ` NeilBrown
2013-06-25 16:46 ` Piergiorgio Sartor
2013-06-27 4:27 ` NeilBrown
2013-06-27 20:49 ` Piergiorgio Sartor
2013-06-27 21:12 ` NeilBrown
2013-06-28 17:46 ` Piergiorgio Sartor
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=20130624170458.568dafcb@notabene.brown \
--to=neilb@suse.de \
--cc=bernd.schubert@itwm.fraunhofer.de \
--cc=linux-raid@vger.kernel.org \
--cc=piergiorgio.sartor@nexgo.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).