diff mbox series

powerpc: Drop unused CONFIG_PPC_HAS_FEATURE_CALLS

Message ID 20211203115755.2906587-1-mpe@ellerman.id.au (mailing list archive)
State Superseded
Headers show
Series powerpc: Drop unused CONFIG_PPC_HAS_FEATURE_CALLS | expand

Checks

Context Check Description
snowpatch_ozlabs/github-powerpc_selftests success Successfully ran 8 jobs.
snowpatch_ozlabs/github-powerpc_ppctests warning ppctests (ubuntu-21.04, ppc64) found 2 issues.
snowpatch_ozlabs/github-powerpc_sparse success Successfully ran 4 jobs.
snowpatch_ozlabs/github-powerpc_clang success Successfully ran 7 jobs.
snowpatch_ozlabs/github-powerpc_kernel_qemu success Successfully ran 24 jobs.

Commit Message

Michael Ellerman Dec. 3, 2021, 11:57 a.m. UTC
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 mbox series

Patch

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;