From: Neil Brown <neilb@suse.de>
To: Dan Williams <dan.j.williams@intel.com>
Cc: ed.ciechanowski@intel.com, marcin.labun@intel.com,
linux-raid@vger.kernel.org
Subject: Re: [GIT PATCH 0/2] external-metadata recovery checkpointing for 2.6.33
Date: Mon, 14 Dec 2009 16:35:02 +1100 [thread overview]
Message-ID: <20091214163502.5336f303@notabene.brown> (raw)
In-Reply-To: <e9c3a7c20912132049g6034fbc6vf86a7bcbc323746a@mail.gmail.com>
On Sun, 13 Dec 2009 21:49:07 -0700
Dan Williams <dan.j.williams@intel.com> wrote:
> > +static ssize_t recovery_start_store(mdk_rdev_t *rdev, const char *buf, size_t len)
> > +{
> > + unsigned long long recovery_start;
> > +
> > + if (cmd_match(buf, "none"))
> > + recovery_start = MaxSector;
>
> Should probably do the same for resync_start to be consistent?
Good idea, thanks.
I've resubmitted the pull request for all the 2.6.33 patches.
Thanks,
NeilBrown
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-12-14 5:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-13 4:17 [GIT PATCH 0/2] external-metadata recovery checkpointing for 2.6.33 Dan Williams
2009-12-13 4:17 ` [PATCH 1/2] md: rcu_read_lock() walk of mddev->disks in md_do_sync() Dan Williams
2009-12-13 4:17 ` [PATCH 2/2] md: add 'recovery_start' sysfs attribute Dan Williams
2009-12-14 4:07 ` [GIT PATCH 0/2] external-metadata recovery checkpointing for 2.6.33 Neil Brown
2009-12-14 4:49 ` Dan Williams
2009-12-14 5:35 ` Neil Brown [this message]
2009-12-15 0:37 ` Dan Williams
2009-12-15 4:19 ` Dan Williams
2009-12-15 18:03 ` Dan Williams
2009-12-16 5:16 ` Neil Brown
2009-12-16 6:24 ` Dan Williams
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=20091214163502.5336f303@notabene.brown \
--to=neilb@suse.de \
--cc=dan.j.williams@intel.com \
--cc=ed.ciechanowski@intel.com \
--cc=linux-raid@vger.kernel.org \
--cc=marcin.labun@intel.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).