All of lore.kernel.org
 help / color / mirror / Atom feed
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/5] rbd: drop some unneeded parameters
Date: Tue, 15 Jan 2013 17:46:38 -0800	[thread overview]
Message-ID: <50F6067E.2050604@inktank.com> (raw)
In-Reply-To: <50E61175.7010103@inktank.com>

On 01/03/2013 03:17 PM, Alex Elder wrote:
> This series cleans up some parameter lists, eliminating parameters
> that don't need to be used.
>
> 					-Alex
>
> [PATCH REPOST 1/5] rbd: drop oid parameters from ceph_osdc_build_request()
> [PATCH REPOST 2/5] rbd: drop snapid parameter from rbd_req_sync_read()
> [PATCH REPOST 3/5] rbd: drop flags parameter from rbd_req_sync_exec()
> [PATCH REPOST 4/5] rbd: kill rbd_req_sync_op() snapc and snapid parameters
> [PATCH REPOST 5/5] rbd: don't bother setting snapid in rbd_do_request()

These look good to me.

Reviewed-by: Josh Durgin <josh.durgin@inktank.com>


      parent reply	other threads:[~2013-01-16  1:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-03 23:17 [PATCH REPOST 0/5] rbd: drop some unneeded parameters Alex Elder
2013-01-03 23:18 ` [PATCH REPOST 1/5] rbd: drop oid parameters from ceph_osdc_build_request() Alex Elder
2013-01-03 23:18 ` [PATCH REPOST 2/5] rbd: drop snapid parameter from rbd_req_sync_read() Alex Elder
2013-01-03 23:19 ` [PATCH REPOST 3/5] rbd: drop flags parameter from rbd_req_sync_exec() Alex Elder
2013-01-03 23:19 ` [PATCH REPOST 4/5] rbd: kill rbd_req_sync_op() snapc and snapid parameters Alex Elder
2013-01-03 23:19 ` [PATCH REPOST 5/5] rbd: don't bother setting snapid in rbd_do_request() Alex Elder
2013-01-16  1:46 ` 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=50F6067E.2050604@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.