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 17:34:06 +1100 [thread overview]
Message-ID: <20110131173406.1c69d042@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.
All the acceptable patches are now in my devel-3.2 branch
git://neil.brown.name/mdadm devel-3.2
It still doesn't pass all of my self-tests, though it is getting closer.
Hopefully it will pass them all tomorrow.
>
> I would also mention that we expect that the kernel patches will be applied.
All the acceptable patches are now in my for-next branch:
git://neil.brown.name/md for-next
Others have been replied to.
NeilBrown
prev parent reply other threads:[~2011-01-31 6:34 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
2011-01-31 6:34 ` NeilBrown [this message]
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=20110131173406.1c69d042@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).