From: Ilya Dryomov <idryomov@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: ceph-devel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Ceph fixes for 4.13-rc4
Date: Fri, 4 Aug 2017 17:23:04 +0200 [thread overview]
Message-ID: <1501860184-26226-1-git-send-email-idryomov@gmail.com> (raw)
Hi Linus,
The following changes since commit 16f73eb02d7e1765ccab3d2018e0bd98eb93d973:
Linux 4.13-rc3 (2017-07-30 12:40:36 -0700)
are available in the git repository at:
https://github.com/ceph/ceph-client.git tags/ceph-for-4.13-rc4
for you to fetch changes up to ae78dd8139ce93a528beb7f3914531b7a7be9e30:
libceph: make RECOVERY_DELETES feature create a new interval (2017-08-01 16:46:45 +0200)
----------------------------------------------------------------
A bunch of fixes and follow-ups for -rc1 Luminous patches: issues with
->reencode_message() and last minute RADOS semantic changes in v12.1.2.
----------------------------------------------------------------
Ilya Dryomov (6):
libceph: make encode_request_*() work with r_mempool requests
libceph: don't call ->reencode_message() more than once per message
libceph: fallback for when there isn't a pool-specific choose_arg
crush: assume weight_set != null imples weight_set_size > 0
libceph: upmap semantic changes
libceph: make RECOVERY_DELETES feature create a new interval
include/linux/ceph/osd_client.h | 1 +
include/linux/ceph/osdmap.h | 2 ++
include/linux/ceph/rados.h | 4 +++
include/linux/crush/crush.h | 2 +-
net/ceph/crush/mapper.c | 2 +-
net/ceph/messenger.c | 6 ++---
net/ceph/osd_client.c | 14 +++++++---
net/ceph/osdmap.c | 60 ++++++++++++++++++++---------------------
8 files changed, 53 insertions(+), 38 deletions(-)
reply other threads:[~2017-08-04 15:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1501860184-26226-1-git-send-email-idryomov@gmail.com \
--to=idryomov@gmail.com \
--cc=ceph-devel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®