From: "Aneesh Kumar K. V" <aneesh.kumar@linux.vnet.ibm.com>
To: Sage Weil <sage@newdream.net>
Cc: ceph-devel@vger.kernel.org
Subject: Re: [PATCH 1/2] ceph: Fix return value of encode_fh function
Date: Tue, 05 Oct 2010 23:15:17 +0530 [thread overview]
Message-ID: <m3d3rojzyq.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1010051001480.21681@cobra.newdream.net>
On Tue, 5 Oct 2010 10:02:34 -0700 (PDT), Sage Weil <sage@newdream.net> wrote:
> Aneesh,
>
> I'll add these to my tree (unless you want to send them separately?).
>
They can go via your tree.
-aneesh
prev parent reply other threads:[~2010-10-05 17:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-05 10:33 [PATCH 1/2] ceph: Fix return value of encode_fh function Aneesh Kumar K.V
2010-10-05 10:33 ` [PATCH 2/2] ceph: Update max_len with minimum required size Aneesh Kumar K.V
2010-10-05 17:02 ` [PATCH 1/2] ceph: Fix return value of encode_fh function Sage Weil
2010-10-05 17:45 ` Aneesh Kumar K. V [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=m3d3rojzyq.fsf@linux.vnet.ibm.com \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=ceph-devel@vger.kernel.org \
--cc=sage@newdream.net \
/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