From: Michael Ellerman <mpe@ellerman.id.au>
To: <linuxppc-dev@lists.ozlabs.org>
Subject: [PATCH] powerpc: Drop unused CONFIG_PPC_HAS_FEATURE_CALLS
Date: Fri, 3 Dec 2021 22:57:55 +1100 [thread overview]
Message-ID: <20211203115755.2906587-1-mpe@ellerman.id.au> (raw)
Since ~2002 we have had CONFIG_PPC_HAS_FEATURE_CALLS defined as a faux
CONFIG symbol, firstly in include/asm-ppc/machdep.h, and then later
copied over to powerpc when ppc and ppc64 were merged.
The last in-tree usage was removed in 2005 in commit
7bbd827750e6 ("[PATCH] ppc64: very basic desktop g5 sound support").
I haven't been able to find any meaningful references to it anywhere
else, so I suspect it has been unused for many years. It confuses
scripts/checkkconfigsymbols.py, and seems to serve no purpose, so drop
it.
Note that it's not in a uapi header, ie. it could only be used by
out-of-tree kernel modules, not general userspace code.
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
---
If anything does use it, just let us know.
---
arch/powerpc/include/asm/machdep.h | 5 -----
1 file changed, 5 deletions(-)
diff --git a/arch/powerpc/include/asm/machdep.h b/arch/powerpc/include/asm/machdep.h
index e821037f74f0..75687e1f994a 100644
--- a/arch/powerpc/include/asm/machdep.h
+++ b/arch/powerpc/include/asm/machdep.h
@@ -10,11 +10,6 @@
#include <asm/setup.h>
-/* We export this macro for external modules like Alsa to know if
- * ppc_md.feature_call is implemented or not
- */
-#define CONFIG_PPC_HAS_FEATURE_CALLS
-
struct pt_regs;
struct pci_bus;
struct device_node;
--
2.31.1
reply other threads:[~2021-12-03 11:58 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=20211203115755.2906587-1-mpe@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=linuxppc-dev@lists.ozlabs.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