From: Alex Elder <elder@inktank.com>
To: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: [PATCH REPOST 0/4] rbd: four minor patches
Date: Thu, 03 Jan 2013 13:04:33 -0600 [thread overview]
Message-ID: <50E5D641.2010405@inktank.com> (raw)
I'm re-posting my patch backlog, in chunks that may or may not
match how they got posted before. This series contains some
pretty fairly straightforward changes.
-Alex
[PATCH REPOST 1/4] rbd: document rbd_spec structure
[PATCH REPOST 2/4] rbd: kill rbd_spec->image_name_len
[PATCH REPOST 3/4] rbd: kill rbd_spec->image_id_len
[PATCH REPOST 4/4] rbd: use kmemdup()
next reply other threads:[~2013-01-03 19:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-03 19:04 Alex Elder [this message]
2013-01-03 19:05 ` [PATCH REPOST 1/4] rbd: document rbd_spec structure Alex Elder
2013-01-03 19:06 ` [PATCH REPOST 2/4] rbd: kill rbd_spec->image_name_len Alex Elder
2013-01-03 19:06 ` [PATCH REPOST 3/4] rbd: kill rbd_spec->image_id_len Alex Elder
2013-01-03 19:06 ` [PATCH REPOST 4/4] rbd: use kmemdup() Alex Elder
2013-01-03 22:55 ` [PATCH REPOST 0/4] rbd: four minor patches David Zafman
2013-01-16 1:29 ` 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=50E5D641.2010405@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