From: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>
To: NeilBrown <neilb@suse.de>
Cc: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>,
Bernd Schubert <bernd.schubert@itwm.fraunhofer.de>,
linux-raid@vger.kernel.org
Subject: Re: [PATCH 0/6] raid6check fixes
Date: Tue, 25 Jun 2013 18:46:28 +0200 [thread overview]
Message-ID: <20130625164628.GA2261@lazy.lzy> (raw)
In-Reply-To: <20130625095422.29d3079b@notabene.brown>
On Tue, Jun 25, 2013 at 09:54:22AM +1000, NeilBrown wrote:
[...]
> I don't remember holding back on any raid6check patches, but then I tend to
> forget such things - usually after I've replied with why, but sometimes
> before.
>
> If there are patches that you (or anyone else) think should be in but aren't,
> please point them out to me. I'll either apply them or explain why I don't
> want to.
Hi Neil,
no, you did not seem to have forgot anything.
I quickly checked mdadm-3.3-rc1 source and it
seems raid6check.c is up to date.
> > > 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.
> >
> > Well, that could be some thinking for 3.3, couldn't it? :-)
>
> It could indeed.
Well, do not forget... :-)
Thanks,
bye,
pg
> Thanks,
> NeilBrown
>
>
> >
> > In any case, yes, it would be nice to force a bit
> > the hand of the distros by installing "raid6check" too.
> >
> > Thanks,
> >
> > bye,
> >
> > pg
> >
> > > NeilBrown
> > >
> > > >
> > > > Thanks,
> > > >
> > > > bye,
> > > >
> > >
> >
> >
> >
>
--
piergiorgio
next prev parent reply other threads:[~2013-06-25 16:46 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
2013-06-24 17:10 ` Piergiorgio Sartor
2013-06-24 23:54 ` NeilBrown
2013-06-25 16:46 ` Piergiorgio Sartor [this message]
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=20130625164628.GA2261@lazy.lzy \
--to=piergiorgio.sartor@nexgo.de \
--cc=bernd.schubert@itwm.fraunhofer.de \
--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).