From: linux@treblig.org
To: xiubli@redhat.com, idryomov@gmail.com, ceph-devel@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
"Dr. David Alan Gilbert" <linux@treblig.org>
Subject: [PATCH 0/5] Ceph deadcoding
Date: Sun, 6 Oct 2024 02:19:51 +0100 [thread overview]
Message-ID: <20241006011956.373622-1-linux@treblig.org> (raw)
From: "Dr. David Alan Gilbert" <linux@treblig.org>
Hi,
This series is a set of deadcoding in fs/ceph and net/ceph.
It's strictly function deletion so should have no change
in behaviour.
(get_maintainer was suggesting the netdev team as well
as ceph? Is that correct???)
Build & boot tested on x86-64.
Dave
Dr. David Alan Gilbert (5):
libceph: Remove unused ceph_pagelist functions
libceph: Remove unused pagevec functions
libceph: Remove unused ceph_osdc_watch_check
libceph: Remove unused ceph_crypto_key_encode
ceph: Remove fs/ceph deadcode
fs/ceph/caps.c | 14 ---------
fs/ceph/mds_client.c | 8 -----
fs/ceph/mds_client.h | 2 --
fs/ceph/super.h | 1 -
include/linux/ceph/libceph.h | 6 ----
include/linux/ceph/osd_client.h | 2 --
include/linux/ceph/pagelist.h | 12 --------
net/ceph/crypto.c | 12 --------
net/ceph/crypto.h | 1 -
net/ceph/osd_client.c | 34 ---------------------
net/ceph/pagelist.c | 38 ------------------------
net/ceph/pagevec.c | 52 ---------------------------------
12 files changed, 182 deletions(-)
--
2.46.2
next reply other threads:[~2024-10-06 1:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-06 1:19 linux [this message]
2024-10-06 1:19 ` [PATCH 1/5] libceph: Remove unused ceph_pagelist functions linux
2024-10-06 1:19 ` [PATCH 2/5] libceph: Remove unused pagevec functions linux
2024-10-06 1:19 ` [PATCH 3/5] libceph: Remove unused ceph_osdc_watch_check linux
2024-10-06 1:19 ` [PATCH 4/5] libceph: Remove unused ceph_crypto_key_encode linux
2024-10-06 1:19 ` [PATCH 5/5] ceph: Remove fs/ceph deadcode linux
2024-10-27 19:53 ` [PATCH 0/5] Ceph deadcoding Ilya Dryomov
2024-10-27 20:16 ` Ilya Dryomov
2024-10-27 20:45 ` Dr. David Alan Gilbert
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=20241006011956.373622-1-linux@treblig.org \
--to=linux@treblig.org \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xiubli@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome