All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Elder <elder@inktank.com>
To: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Patch Backlog
Date: Fri, 09 Nov 2012 21:57:16 -0600	[thread overview]
Message-ID: <509DD09C.4030506@inktank.com> (raw)

Below is the list of patches that I have posted in
the last week or so that have not yet been reviewed.

There is nothing very tricky about any of them, so if
you think you can take a look and give it your stamp of
approval (or offer suggestions for improvement) I'd
love to hear about it.  New people, here's your chance
to contribute!

Thanks.

					-Alex

[PATCH 1/5] rbd: document rbd_spec structure
[PATCH 2/5] rbd: kill rbd_spec->image_name_len
[PATCH 3/5] rbd: kill rbd_spec->image_id_len
[PATCH 4/5] rbd: don't use ENOTSUPP
[PATCH 5/5] rbd: use kmemdup()

[PATCH] ceph: define ceph_encode_8_safe()

[PATCH] rbd: fix ceph_pg_poolid_by_name()

[PATCH 1/4] rbd: define and use rbd_warn()
[PATCH 2/4] rbd: add warning messages for missing arguments
[PATCH 3/4] rbd: add a warning in bio_chain_clone_range()
[PATCH 4/4] rbd: add warnings to rbd_dev_probe_update_spec()

[PATCH 1/3] rbd: standardize rbd_request variable names
[PATCH 2/3] rbd: standardize ceph_osd_request variable names
[PATCH 3/3] rbd: be picky about osd request status type

[PATCH 1/2] rbd: encapsulate handling for a single request
[PATCH 2/2] rbd: a little more cleanup of rbd_rq_fn()

[PATCH] rbd: end request on error in rbd_do_request() caller

[PATCH 8/5] rbd: fix reference leak in rbd_do_op()
[PATCH 9/5] rbd: only get snap context for write requests

[PATCH] rbd: separate layout init

[PATCH 1/4] rbd: drop oid parameters from
[PATCH 2/4] rbd: drop snapid parameter from rbd_req_sync_read()
[PATCH 3/4] rbd: drop flags parameter from rbd_req_sync_exec()
[PATCH 4/4] rbd: kill rbd_req_sync_op() snapc and snapid

[PATCH] rbd: don't bother setting snapid in rbd_do_request()

[PATCH] rbd: get rid of RBD_MAX_SEG_NAME_LEN

             reply	other threads:[~2012-11-10  3:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-10  3:57 Alex Elder [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-12-31 22:52 Patch Backlog Alex Elder

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=509DD09C.4030506@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.