CEPH filesystem development
 help / color / mirror / Atom feed
From: Alex Elder <elder@inktank.com>
To: ceph-devel@vger.kernel.org
Subject: Re: [PATCH 00/12] rbd: cleanup series
Date: Thu, 26 Jul 2012 13:22:37 -0500	[thread overview]
Message-ID: <50118AED.8070200@inktank.com> (raw)
In-Reply-To: <500874F5.4090205@inktank.com>

On 07/19/2012 03:58 PM, Alex Elder wrote:
> This series includes a bunch of relatively small cleanups.
> They're grouped a bit below, but they apply together in
> this sequence and the later ones may have dependencies on
> those earlier in the series.

None of these were reviewed, so I'm re-submitting them.  I
have a few more to add, and may have rearranged the order
a bit since last time.  In any case, if you intend to review
anything please disregard this series and look at the patches
I'm about to post instead.

					-Alex


> Summaries:
> [PATCH 01/12] rbd: drop extra header_rwsem init
> [PATCH 02/12] rbd: simplify __rbd_remove_all_snaps()
> [PATCH 03/12] rbd: clean up a few dout() calls
> [PATCH 04/12] ceph: define snap counts as u32 everywhere
>     These four are very simple and straightforward cleanups.
> 
> [PATCH 05/12] rbd: snapc is unused in rbd_req_sync_read()
> [PATCH 06/12] rbd: drop rbd_header_from_disk() gfp_flags parameter
> [PATCH 07/12] rbd: drop rbd_dev parameter in snap functions
> [PATCH 08/12] rbd: drop rbd_req_sync_exec() "ver" parameter
>     These four each drop an unused argument from a function.
> 
> [PATCH 09/12] rbd: have __rbd_add_snap_dev() return a pointer
> [PATCH 10/12] rbd: make rbd_create_rw_ops() return a pointer
>     These two each change a function so it returns a pointer
>     rather than filling in the address of a provided pointer.
> 
> [PATCH 11/12] rbd: always pass ops array to rbd_req_sync_op()
> [PATCH 12/12] rbd: fixes in rbd_header_from_disk()
>     These comprise slightly more involved refactoring of the
>     code, but as with the rest of the patches in this series,
>     there should be no functional difference as a result.
> 
> 					-Alex
> 


      parent reply	other threads:[~2012-07-26 18:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-19 20:58 [PATCH 00/12] rbd: cleanup series Alex Elder
2012-07-19 21:08 ` [PATCH 01/12] rbd: drop extra header_rwsem init Alex Elder
2012-07-19 21:08 ` [PATCH 02/12] rbd: simplify __rbd_remove_all_snaps() Alex Elder
2012-07-19 21:08 ` [PATCH 03/12] rbd: clean up a few dout() calls Alex Elder
2012-07-19 21:08 ` [PATCH 04/12] ceph: define snap counts as u32 everywhere Alex Elder
2012-07-19 21:08 ` [PATCH 05/12] rbd: snapc is unused in rbd_req_sync_read() Alex Elder
2012-07-19 21:08 ` [PATCH 06/12] rbd: drop rbd_header_from_disk() gfp_flags parameter Alex Elder
2012-07-19 21:08 ` [PATCH 07/12] rbd: drop rbd_dev parameter in snap functions Alex Elder
2012-07-19 21:08 ` [PATCH 08/12] rbd: drop rbd_req_sync_exec() "ver" parameter Alex Elder
2012-07-19 21:08 ` [PATCH 09/12] rbd: have __rbd_add_snap_dev() return a pointer Alex Elder
2012-07-19 21:08 ` [PATCH 10/12] rbd: make rbd_create_rw_ops() " Alex Elder
2012-07-19 21:09 ` [PATCH 11/12] rbd: always pass ops array to rbd_req_sync_op() Alex Elder
2012-07-19 21:09 ` [PATCH 12/12] rbd: fixes in rbd_header_from_disk() Alex Elder
2012-07-26 18:22 ` Alex Elder [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=50118AED.8070200@inktank.com \
    --to=elder@inktank.com \
    --cc=ceph-devel@vger.kernel.org \
    /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