From: Kefu Chai <k.chai@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH v2 ceph 0/1] patches: drop patch disabling elastic_shared_blobs workaround
Date: Wed, 24 Jun 2026 15:42:26 +0800 [thread overview]
Message-ID: <20260624074228.3807165-1-k.chai@proxmox.com> (raw)
PR #65964 (commit 04d1d8ad575, Tentacle 20.2.1) fixed tracker#70390.
The workaround is no longer needed.
Changes since v1:
- rebased onto Tentacle 20.2.2; patch shifted from 0010 to 0009
(py3dist was dropped in the 20.2.1 refresh), one fewer patch renumbered
Kefu Chai (1):
patches: drop patch disabling elastic_shared_blobs workaround
...09-d-rules-disable-jaeger-telemetry.patch} | 0
...shared_blob-to-prevent-crashing-OSDs.patch | 33 -------------------
...p-legacy-init.d-ceph-script-anymore.patch} | 0
...port-by-making-NOTIFY_TYPES-in-py-m.patch} | 0
...e-on_progress-callbacks-to-prevent-.patch} | 0
patches/series | 9 +++--
6 files changed, 4 insertions(+), 38 deletions(-)
rename patches/{0010-d-rules-disable-jaeger-telemetry.patch => 0009-d-rules-disable-jaeger-telemetry.patch} (100%)
delete mode 100644 patches/0009-disable-elastic_shared_blob-to-prevent-crashing-OSDs.patch
rename patches/{0011-debian-do-not-ship-legacy-init.d-ceph-script-anymore.patch => 0010-debian-do-not-ship-legacy-init.d-ceph-script-anymore.patch} (100%)
rename patches/{0012-mgr-fix-module-import-by-making-NOTIFY_TYPES-in-py-m.patch => 0011-mgr-fix-module-import-by-making-NOTIFY_TYPES-in-py-m.patch} (100%)
rename patches/{0013-pybind-rbd-disable-on_progress-callbacks-to-prevent-.patch => 0012-pybind-rbd-disable-on_progress-callbacks-to-prevent-.patch} (100%)
--
2.47.3
next reply other threads:[~2026-06-24 7:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-24 7:42 Kefu Chai [this message]
2026-06-24 7:42 ` [PATCH v2 ceph 1/1] patches: drop patch disabling elastic_shared_blobs workaround Kefu Chai
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=20260624074228.3807165-1-k.chai@proxmox.com \
--to=k.chai@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/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.