From: Josh Durgin <josh.durgin@inktank.com>
To: Alex Elder <elder@inktank.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: [PATCH 0/7] rbd: drop unused parameters from functions
Date: Thu, 26 Jul 2012 12:35:24 -0700 [thread overview]
Message-ID: <50119BFC.6050306@inktank.com> (raw)
In-Reply-To: <50119076.1030307@inktank.com>
On 07/26/2012 11:46 AM, Alex Elder wrote:
> All the patches in this series just drop unused parameters from
> their functions.
>
> -Alex
>
> [PATCH 1/7] rbd: snapc is unused in rbd_req_sync_read()
> [PATCH 2/7] rbd: drop rbd_header_from_disk() gfp_flags parameter
> [PATCH 3/7] rbd: drop rbd_dev parameter in snap functions
> [PATCH 4/7] rbd: drop "object_name" from rbd_req_sync_watch()
> [PATCH 5/7] rbd: drop "object_name" from rbd_req_sync_notify()
> [PATCH 6/7] rbd: drop "object_name" from rbd_req_sync_notify_ack()
> [PATCH 7/7] rbd: drop "object_name" from rbd_req_sync_unwatch()
Reviewed-by: Josh Durgin <josh.durgin@inktank.com>
prev parent reply other threads:[~2012-07-26 19:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 18:46 [PATCH 0/7] rbd: drop unused parameters from functions Alex Elder
2012-07-26 18:57 ` [PATCH 1/7] rbd: snapc is unused in rbd_req_sync_read() Alex Elder
2012-07-26 18:57 ` [PATCH 2/7] rbd: drop rbd_header_from_disk() gfp_flags parameter Alex Elder
2012-07-26 18:57 ` [PATCH 3/7] rbd: drop rbd_dev parameter in snap functions Alex Elder
2012-07-26 18:57 ` [PATCH 4/7] rbd: drop "object_name" from rbd_req_sync_watch() Alex Elder
2012-07-26 18:57 ` [PATCH 5/7] rbd: drop "object_name" from rbd_req_sync_notify() Alex Elder
2012-07-26 18:57 ` [PATCH 6/7] rbd: drop "object_name" from rbd_req_sync_notify_ack() Alex Elder
2012-07-26 18:57 ` [PATCH 7/7] rbd: drop "object_name" from rbd_req_sync_unwatch() Alex Elder
2012-07-26 19:35 ` 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=50119BFC.6050306@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