From: Alison Schofield <alison.schofield@intel.com>
To: linux@treblig.org
Cc: dan.j.williams@intel.com, vishal.l.verma@intel.com,
dave.jiang@intel.com, ira.weiny@intel.com,
nvdimm@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] nvdimm deadcoding
Date: Thu, 20 Feb 2025 12:37:45 -0800 [thread overview]
Message-ID: <Z7eSmfcdNeYr1rWa@aschofie-mobl2.lan> (raw)
In-Reply-To: <20250220004538.84585-1-linux@treblig.org>
On Thu, Feb 20, 2025 at 12:45:36AM +0000, linux@treblig.org wrote:
> From: "Dr. David Alan Gilbert" <linux@treblig.org>
>
> Hi,
> A couple of nvdimm dead coding patches; they just
> remove entirely unused functions.
I see you've been sending patches for dead code removal
for several months. What tool are you using for discovery?
Thanks,
Alison
>
> Signed-off-by: Dr. David Alan Gilbert <linux@treblig.org>
>
>
> Dr. David Alan Gilbert (2):
> libnvdimm: Remove unused nd_region_conflict
> libnvdimm: Remove unused nd_attach_ndns
>
> drivers/nvdimm/claim.c | 11 ----------
> drivers/nvdimm/nd-core.h | 4 ----
> drivers/nvdimm/region_devs.c | 41 ------------------------------------
> 3 files changed, 56 deletions(-)
>
> --
> 2.48.1
>
>
next prev parent reply other threads:[~2025-02-20 20:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-20 0:45 [PATCH 0/2] nvdimm deadcoding linux
2025-02-20 0:45 ` [PATCH 1/2] libnvdimm: Remove unused nd_region_conflict linux
2025-02-20 0:45 ` [PATCH 2/2] libnvdimm: Remove unused nd_attach_ndns linux
2025-02-20 19:10 ` [PATCH 0/2] nvdimm deadcoding Ira Weiny
2025-02-20 20:37 ` Alison Schofield [this message]
2025-02-20 21:51 ` 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=Z7eSmfcdNeYr1rWa@aschofie-mobl2.lan \
--to=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=ira.weiny@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@treblig.org \
--cc=nvdimm@lists.linux.dev \
--cc=vishal.l.verma@intel.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