From: Benny Halevy <bhalevy@panasas.com>
To: Jim Rees <rees@umich.edu>
Cc: linux-nfs@vger.kernel.org, Eric Anderle <eanderle@umich.edu>,
peter honeyman <honey@citi.umich.edu>
Subject: Re: [PATCH] nfs-utils: Various bug fixes and cleanups to blkmapd
Date: Wed, 03 Nov 2010 17:02:06 +0200 [thread overview]
Message-ID: <4CD1796E.2020006@panasas.com> (raw)
In-Reply-To: <20101102140522.GA23409-8f4Pc2RrbJmHXe+LvDLADg@public.gmane.org>
On 2010-11-02 16:05, Jim Rees wrote:
> Benny Halevy wrote:
>
> There are conflicts merging this patch as bldev_read_ap_state
> is already defined (in "Add complex block layout discovery and mapping daemon")
> I'm not sure how, but we seem out of sync, maybe I didn't get an earlier patch
> of yours.
>
> My patches are all in your pnfs-nfs-utils-1-2-3-2010-10-08 but are missing
> after that. I will re-send.
Sorry about that. Thanks for tracking this down and resending!
Benny
>
> % git shortlog --author=rees@umich pnfs-nfs-utils-1-2-3-2010-10-08
> Jim Rees (5):
> Add complex block layout discovery and mapping daemon
> blkmapd: get rid of config file and instead examine all block devices
> blkmapd: don't rescan periodically
> blkmapd: don't use atomicio() where it's not needed
> blkmapd: don't try to distinguish between active/passive devices
>
> % git shortlog --author=rees@umich origin/master
> Jim Rees (1):
> Add complex block layout discovery and mapping daemon
prev parent reply other threads:[~2010-11-03 15:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-29 15:36 [PATCH] nfs-utils: Various bug fixes and cleanups to blkmapd Jim Rees
2010-11-02 6:34 ` Benny Halevy
2010-11-02 11:34 ` Jim Rees
2010-11-02 14:05 ` Jim Rees
[not found] ` <20101102140522.GA23409-8f4Pc2RrbJmHXe+LvDLADg@public.gmane.org>
2010-11-03 15:02 ` Benny Halevy [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=4CD1796E.2020006@panasas.com \
--to=bhalevy@panasas.com \
--cc=eanderle@umich.edu \
--cc=honey@citi.umich.edu \
--cc=linux-nfs@vger.kernel.org \
--cc=rees@umich.edu \
/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).