From: Josh Durgin <josh.durgin@inktank.com>
To: Alex Elder <elder@inktank.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: [PATCH REPOST 0/6] libceph: parameter cleanup
Date: Wed, 16 Jan 2013 15:12:23 -0800 [thread overview]
Message-ID: <50F733D7.7030407@inktank.com> (raw)
In-Reply-To: <50E6E7C2.2020604@inktank.com>
On 01/04/2013 06:31 AM, Alex Elder wrote:
> This series mostly cleans up parameters used by functions
> in libceph, in the osd client code.
>
> -Alex
>
> [PATCH REPOST 1/6] libceph: pass length to ceph_osdc_build_request()
> [PATCH REPOST 2/6] libceph: pass length to ceph_calc_file_object_mapping()
> [PATCH REPOST 3/6] libceph: drop snapid in ceph_calc_raw_layout()
> [PATCH REPOST 4/6] libceph: drop osdc from ceph_calc_raw_layout()
> [PATCH REPOST 5/6] libceph: don't set flags in ceph_osdc_alloc_request()
> [PATCH REPOST 6/6] libceph: don't set pages or bio in
> ceph_osdc_alloc_request()
These all look good.
Reviewed-by: Josh Durgin <josh.durgin@inktank.com>
prev parent reply other threads:[~2013-01-16 23:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-04 14:31 [PATCH REPOST 0/6] libceph: parameter cleanup Alex Elder
2013-01-04 14:33 ` [PATCH REPOST 1/6] libceph: pass length to ceph_osdc_build_request() Alex Elder
2013-01-04 14:33 ` [PATCH REPOST 2/6] libceph: pass length to ceph_calc_file_object_mapping() Alex Elder
2013-01-04 14:33 ` [PATCH REPOST 3/6] libceph: drop snapid in ceph_calc_raw_layout() Alex Elder
2013-01-04 14:33 ` [PATCH REPOST 4/6] libceph: drop osdc from ceph_calc_raw_layout() Alex Elder
2013-01-04 14:34 ` [PATCH REPOST 5/6] libceph: don't set flags in ceph_osdc_alloc_request() Alex Elder
2013-01-04 14:34 ` [PATCH REPOST 6/6] libceph: don't set pages or bio in,> ceph_osdc_alloc_request() Alex Elder
2013-01-16 23:12 ` Josh Durgin [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=50F733D7.7030407@inktank.com \
--to=josh.durgin@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=elder@inktank.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