From: linux@treblig.org
To: robert.moore@intel.com, rafael.j.wysocki@intel.com, lenb@kernel.org
Cc: linux-acpi@vger.kernel.org, acpica-devel@lists.linux.dev,
linux-kernel@vger.kernel.org,
"Dr. David Alan Gilbert" <linux@treblig.org>
Subject: [PATCH] ACPICA: Remove unused 'acpi_ps_get_name'
Date: Sun, 29 Sep 2024 01:02:53 +0100 [thread overview]
Message-ID: <20240929000253.418403-1-linux@treblig.org> (raw)
From: "Dr. David Alan Gilbert" <linux@treblig.org>
acpi_ps_get_name is currently unused, remove it.
I can't find any history of it's use since git, but I can
see it was used in 2.5.0, and see a record of a removal
of uses at Fri Aug 30 00:38:52 2002.
Signed-off-by: Dr. David Alan Gilbert <linux@treblig.org>
---
drivers/acpi/acpica/acparser.h | 2 --
drivers/acpi/acpica/psutils.c | 17 -----------------
2 files changed, 19 deletions(-)
diff --git a/drivers/acpi/acpica/acparser.h b/drivers/acpi/acpica/acparser.h
index 6dad786a382c..3a61853591d3 100644
--- a/drivers/acpi/acpica/acparser.h
+++ b/drivers/acpi/acpica/acparser.h
@@ -207,8 +207,6 @@ void acpi_ps_free_op(union acpi_parse_object *op);
u8 acpi_ps_is_leading_char(u32 c);
-u32 acpi_ps_get_name(union acpi_parse_object *op);
-
void acpi_ps_set_name(union acpi_parse_object *op, u32 name);
/*
diff --git a/drivers/acpi/acpica/psutils.c b/drivers/acpi/acpica/psutils.c
index d550c4af4702..3799ae9f6d39 100644
--- a/drivers/acpi/acpica/psutils.c
+++ b/drivers/acpi/acpica/psutils.c
@@ -181,23 +181,6 @@ u8 acpi_ps_is_leading_char(u32 c)
return ((u8) (c == '_' || (c >= 'A' && c <= 'Z')));
}
-/*
- * Get op's name (4-byte name segment) or 0 if unnamed
- */
-u32 acpi_ps_get_name(union acpi_parse_object * op)
-{
-
- /* The "generic" object has no name associated with it */
-
- if (op->common.flags & ACPI_PARSEOP_GENERIC) {
- return (0);
- }
-
- /* Only the "Extended" parse objects have a name */
-
- return (op->named.name);
-}
-
/*
* Set op's name
*/
--
2.46.2
reply other threads:[~2024-09-29 0:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240929000253.418403-1-linux@treblig.org \
--to=linux@treblig.org \
--cc=acpica-devel@lists.linux.dev \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=robert.moore@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