From: Alex Elder <elder@inktank.com>
To: ceph-devel@vger.kernel.org
Subject: [PATCH 0/2] libceph: update osd_req_encode_op()
Date: Sat, 16 Feb 2013 11:00:02 -0600 [thread overview]
Message-ID: <511FBB12.6050207@inktank.com> (raw)
This series just modifies osd_req_encode_op so it is
more informative, distinguishing between defined but
not supported opcodes and garbage opcodes.
-Alex
[PATCH 1/2] libceph: report defined but unsupported osd ops
[PATCH 2/2] libceph: remove dead code in osd_req_encode_op()
next reply other threads:[~2013-02-16 17:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-16 17:00 Alex Elder [this message]
2013-02-16 17:00 ` [PATCH 1/2] libceph: report defined but unsupported osd ops Alex Elder
2013-02-16 17:01 ` [PATCH 2/2] libceph: remove dead code in osd_req_encode_op() Alex Elder
2013-02-16 23:56 ` [PATCH 0/2] libceph: update osd_req_encode_op() Josh Durgin
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=511FBB12.6050207@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.