From: Leon Romanovsky <leon@kernel.org>
To: jgg@ziepe.ca, linux-rdma@vger.kernel.org, linux@treblig.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] RDMA deadcode
Date: Tue, 24 Dec 2024 05:00:56 -0500 [thread overview]
Message-ID: <173503445650.413911.301360503970776645.b4-ty@kernel.org> (raw)
In-Reply-To: <20241221014021.343979-1-linux@treblig.org>
On Sat, 21 Dec 2024 01:40:17 +0000, linux@treblig.org wrote:
> From: "Dr. David Alan Gilbert" <linux@treblig.org>
>
> A small collection of function deadcoding, for functions that
> haven't been used for between 5 and 20 years.
>
> These are all entire function removals, and are build tested
> only.
>
> [...]
Applied, thanks!
[1/4] RDMA/core: Remove unused ib_ud_header_unpack
https://git.kernel.org/rdma/rdma/c/30dd62fa3954cb
[2/4] RDMA/core: Remove unused ib_find_exact_cached_pkey
https://git.kernel.org/rdma/rdma/c/ddc8fab40b9ae3
[3/4] RDMA/core: Remove unused ibdev_printk
https://git.kernel.org/rdma/rdma/c/750efbb9c307f7
[4/4] RDMA/core: Remove unused ib_copy_path_rec_from_user
https://git.kernel.org/rdma/rdma/c/2028c2958775c4
Best regards,
--
Leon Romanovsky <leon@kernel.org>
prev parent reply other threads:[~2024-12-24 10:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-21 1:40 linux
2024-12-21 1:40 ` [PATCH 1/4] RDMA/core: Remove unused ib_ud_header_unpack linux
2024-12-23 3:29 ` Kalesh Anakkur Purayil
2024-12-21 1:40 ` [PATCH 2/4] RDMA/core: Remove unused ib_find_exact_cached_pkey linux
2024-12-23 3:31 ` Kalesh Anakkur Purayil
2024-12-21 1:40 ` [PATCH 3/4] RDMA/core: Remove unused ibdev_printk linux
2024-12-21 1:40 ` [PATCH 4/4] RDMA/core: Remove unused ib_copy_path_rec_from_user linux
2024-12-23 3:28 ` Kalesh Anakkur Purayil
2024-12-24 10:00 ` Leon Romanovsky [this message]
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=173503445650.413911.301360503970776645.b4-ty@kernel.org \
--to=leon@kernel.org \
--cc=jgg@ziepe.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux@treblig.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®