From: Alex Elder <elder@inktank.com>
To: ceph-devel@vger.kernel.org
Subject: Cleanup Patches
Date: Sat, 16 Feb 2013 10:23:55 -0600 [thread overview]
Message-ID: <511FB29B.3060606@inktank.com> (raw)
I'm about to post several series that contain a bunch of
cleanups. The motivation for this is to simplify some code
before setting out to refactor it, to eliminate any unneeded
complexity.
I've grouped them into smaller series though the patches in
a series may not appear to be logically connected.
These have all been tested together though, and were
applied in the sequence shown below. They're available
in the branch "wip-osd-cleanup" on the ceph-client git
repository.
-Alex
[PATCH] libceph: improve packing in struct ceph_osd_req_op
[PATCH 0/4] libceph: get rid of some unneeded function parameters
[PATCH 1/4] ceph: kill ceph_osdc_writepages() "nofail" parameter
[PATCH 2/4] ceph: kill ceph_osdc_writepages() "dosync" parameter
[PATCH 3/4] ceph: kill ceph_osdc_writepages() "flags" parameter
[PATCH 4/4] ceph: kill ceph_osdc_new_request() "num_reply"
[PATCH 0/3] libceph: a few miscellaneous cleanups
[PATCH 1/3] libceph: lock outside send_queued()
[PATCH 2/3] libdeph: don't export ceph_osdc_init() or
[PATCH 3/3] libceph: kill ceph_calc_raw_layout()
[PATCH 0/2] libceph: get rid of unused "one shot" event support
[PATCH 1/2] libceph: kill ceph_osdc_create_event() "one_shot"
[PATCH 2/2] libceph: kill ceph_osdc_wait_event()
[PATCH 0/3] libceph: update rados.h and related code
[PATCH 1/3] libceph: update rados.h
[PATCH 2/3] libceph: add ceph_osd_state_name()
[PATCH 3/3] libceph: update ceph_osd_op_name()
[PATCH 0/2] libceph: update osd_req_encode_op()
[PATCH 1/2] libceph: report defined but unsupported osd ops
[PATCH 2/2] libceph: remove dead code in osd_req_encode_op()
[PATCH 0/2] libceph: update ceph_fs.h and related code
[PATCH 1/2] libceph: update ceph_fs.h
[PATCH 2/2] libceph: update ceph_mds_state_name() and ceph_mds_op_name()
[PATCH] ceph: simplify ceph_sync_write() page_align
[PATCH] libceph: simplify data length calculation
next reply other threads:[~2013-02-16 16:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-16 16:23 Alex Elder [this message]
[not found] <a08621850711140030x7a5c93bex73af16578bb64ca2@mail.gmail.com>
[not found] ` <5c7c368b0711140634y569c8ce8ke4b2e813a2244ce2@mail.gmail.com>
[not found] ` <a08621850711141050q58fd6830g2d2f195b1db987f3@mail.gmail.com>
[not found] ` <a08621850711141310t166dd07cm6e07f8c81a39b95b@mail.gmail.com>
[not found] ` <5c7c368b0711141439u1cb89d82g8ee0928eabbae2a5@mail.gmail.com>
[not found] ` <CADW=+3kVJUw3cXH79u0WxiiCFU2E1a2jVT4R+kD_mi7dMc9qRg@mail.gmail.com>
2014-11-15 23:06 ` Cleanup patches Dušan Čolić
2014-11-15 23:30 ` Edward Shishkin
2014-11-15 23:30 ` Dušan Čolić
2014-11-16 1:28 ` Dušan Čolić
2014-11-16 1:54 ` Dušan Čolić
2014-11-16 8:29 ` Dušan Čolić
2014-11-16 9:50 ` Edward Shishkin
-- strict thread matches above, loose matches on Subject: below --
2004-09-10 15:18 Martin Schwidefsky
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=511FB29B.3060606@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 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.