From: NeilBrown <neilb@suse.de>
To: majianpeng <majianpeng@gmail.com>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: md:Badsector must in valid range of component device.
Date: Sun, 4 Mar 2012 20:32:41 +1100 [thread overview]
Message-ID: <20120304203241.40a407e3@notabene.brown> (raw)
In-Reply-To: <201203011906162346140@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 429 bytes --]
On Thu, 1 Mar 2012 19:11:16 +0800 "majianpeng" <majianpeng@gmail.com> wrote:
> >From 98de4803f7ae4ad49b680db4889bbcd1534c5303 Mon Sep 17 00:00:00 2001
> From: majianpeng <majianpeng@gmail.com>
> Date: Thu, 1 Mar 2012 15:49:56 +0800
> Subject: [PATCH] md:Badsector must in valid range of component device.
Why must bad sector be in the valid range?
i.e. I don't think this patch is necessary.
Thanks,
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2012-03-04 9:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 11:11 md:Badsector must in valid range of component device majianpeng
2012-03-04 9:32 ` 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=20120304203241.40a407e3@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=majianpeng@gmail.com \
/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).