From: "Dr. David Alan Gilbert" <linux@treblig.org>
To: srinivas.kandagatla@linaro.org
Cc: corbet@lwn.net, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] Remove nvmem deadcode
Date: Wed, 2 Apr 2025 17:44:54 +0000 [thread overview]
Message-ID: <Z-13lseyUTqtVhyS@gallifrey> (raw)
In-Reply-To: <20250221015841.209458-1-linux@treblig.org>
* linux@treblig.org (linux@treblig.org) wrote:
> From: "Dr. David Alan Gilbert" <linux@treblig.org>
>
> Hi,
> This series removes some uncalled deadcode in nvmem.
> The third patch probably deserves a bit closer inspection.
>
> The first one removes nvmem_device_cell_read/write functions
> that haven't been used in ~10 years.
>
> The second removes nvmem_add/del_cell_table - again this is
> removing uncalled functions; nvmem_add_cell_table is unused
> after the removal of the Davinci machines.
>
> The third one removes the remaining nvmem_cell_table code - including
> a function that's called ( nvmem_add_cells_from_table ) - but
> my reading is that from the previous patch there's no way for this
> function to do anything active any more since the list it walks is
> empty.
>
> Build tested only.
>
> Signed-off-by: Dr. David Alan Gilbert <linux@treblig.org>
Hi,
I'd appreciate a review on this series if you get a chance.
Dave (cleaning up his patch queue)
>
>
> Dr. David Alan Gilbert (3):
> nvmem: core: Remove unused nvmem_device_cell_(read|write)
> nvmem: core: Remove nvmem_(add|del)_cell_table
> nvmem: core: Remove remains of nvmem_cell_table
>
> Documentation/driver-api/nvmem.rst | 23 ------
> drivers/nvmem/core.c | 126 -----------------------------
> include/linux/nvmem-consumer.h | 4 -
> include/linux/nvmem-provider.h | 24 ------
> 4 files changed, 177 deletions(-)
>
> --
> 2.48.1
>
--
-----Open up your eyes, open up your mind, open up your code -------
/ Dr. David Alan Gilbert | Running GNU/Linux | Happy \
\ dave @ treblig.org | | In Hex /
\ _________________________|_____ http://www.treblig.org |_______/
prev parent reply other threads:[~2025-04-02 17:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 1:58 [PATCH 0/3] Remove nvmem deadcode linux
2025-02-21 1:58 ` [PATCH 1/3] nvmem: core: Remove unused nvmem_device_cell_(read|write) linux
2025-02-21 1:58 ` [PATCH 2/3] nvmem: core: Remove nvmem_(add|del)_cell_table linux
2025-02-21 1:58 ` [PATCH 3/3] nvmem: core: Remove remains of nvmem_cell_table linux
2025-04-02 17:44 ` Dr. David Alan Gilbert [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=Z-13lseyUTqtVhyS@gallifrey \
--to=linux@treblig.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=srinivas.kandagatla@linaro.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;
as well as URLs for NNTP newsgroup(s).