From: NeilBrown <neilb@suse.de>
To: "Wojcik, Krzysztof" <krzysztof.wojcik@intel.com>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>,
"Neubauer, Wojciech" <Wojciech.Neubauer@intel.com>,
"Kwolek, Adam" <adam.kwolek@intel.com>,
"Williams, Dan J" <dan.j.williams@intel.com>,
"Ciechanowski, Ed" <ed.ciechanowski@intel.com>
Subject: Re: [PATCH 0/2] Release 3.2 summary
Date: Mon, 31 Jan 2011 10:44:56 +1100 [thread overview]
Message-ID: <20110131104456.117da756@notabene.brown> (raw)
In-Reply-To: <BE2BFE91933D1B4089447C644860408067042CDE@irsmsx503.ger.corp.intel.com>
On Sat, 29 Jan 2011 17:52:45 +0000 "Wojcik, Krzysztof"
<krzysztof.wojcik@intel.com> wrote:
> Neil,
>
> Thank you for applying last patches.
> It seems that only two patches left to complete features planed for 3.2 release:
> - imsm: Update metadata for second array
> - imsm: FIX: not all disks are released in free_imsm_disks()
>
> Please, apply them if they are meet your requirements.
>
> After the 3.2 release we plan to submit to you next mdadm's features.
This is probably not a good idea. I don't want to add new features to mdadm
until I am sure that the current ones are stable - and I am not.
I need to see lots of testing of the current features - both for IMSM
metadata and for native metadata, including restart of an array that is
undergoing reshape etc.
I also need to do quite a bit of code review. Reviewing each patch as it
goes in is of course important, but it is quite possible to miss things in
that process. The recent changes evolved quite a bit as they were being
developed, so I am far from confident that the final form really is right.
> On Monday I will send you a draft plan our next steps related to mdadm (what and at what time we plan to submit)
> I hope that this will improve our cooperation.
I'll be happy to look over your draft plan and comment on it, but I don't
expect to be reviewing/accepting any patches for new functionality at least
until 3.2.1 is out which will be primarily bug fixes.
NeilBrown
>
> I would also mention that we expect that the kernel patches will be applied.
>
> Regards
> Krzysztof
>
next prev parent reply other threads:[~2011-01-30 23:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-27 16:46 [PATCH 0/2] Release 3.2 summary Krzysztof Wojcik
2011-01-27 16:46 ` [PATCH 1/2] FIX: Remove disks in mdmon for external metadata Krzysztof Wojcik
2011-01-27 16:46 ` [PATCH 2/2] FIX: Meet SET_ARRAY_INFO ioctl requirements Krzysztof Wojcik
2011-01-28 1:26 ` [PATCH 0/2] Release 3.2 summary Neil Brown
2011-01-29 17:52 ` Wojcik, Krzysztof
2011-01-30 23:44 ` NeilBrown [this message]
2011-01-31 6:34 ` NeilBrown
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=20110131104456.117da756@notabene.brown \
--to=neilb@suse.de \
--cc=Wojciech.Neubauer@intel.com \
--cc=adam.kwolek@intel.com \
--cc=dan.j.williams@intel.com \
--cc=ed.ciechanowski@intel.com \
--cc=krzysztof.wojcik@intel.com \
--cc=linux-raid@vger.kernel.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: 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).