a324e9396c
The driver depends on the ADXL component glue and selects it. However, ADXL itself implicitly depends on ACPI and in nonsensical randconfig builds like this: # CONFIG_ACPI is not set CONFIG_ACPI_ADXL=y where ACPI is not enabled, the build fails with: drivers/edac/skx_edac.o: In function `skx_mce_check_error': skx_edac.c:(.text+0xab): undefined reference to `adxl_decode' drivers/edac/skx_edac.o: In function `skx_init': skx_edac.c:(.init.text+0x8bf): undefined reference to `adxl_get_component_names' make: *** [vmlinux] Error 1 Add stubs for that case so that the build succeeds. CONFIG_ACPI=n doesn't make any sense for real configurations but this fix will at least silence randconfig builds. Signed-off-by: Borislav Petkov <bp@suse.de> Acked-by: Tony Luck <tony.luck@intel.com> Cc: "Rafael J. Wysocki" <rafael@kernel.org>
19 lines
521 B
C
19 lines
521 B
C
/* SPDX-License-Identifier: GPL-2.0 */
|
|
/*
|
|
* Address translation interface via ACPI DSM.
|
|
* Copyright (C) 2018 Intel Corporation
|
|
*/
|
|
|
|
#ifndef _LINUX_ADXL_H
|
|
#define _LINUX_ADXL_H
|
|
|
|
#ifdef CONFIG_ACPI_ADXL
|
|
const char * const *adxl_get_component_names(void);
|
|
int adxl_decode(u64 addr, u64 component_values[]);
|
|
#else
|
|
static inline const char * const *adxl_get_component_names(void) { return NULL; }
|
|
static inline int adxl_decode(u64 addr, u64 component_values[]) { return -EOPNOTSUPP; }
|
|
#endif
|
|
|
|
#endif /* _LINUX_ADXL_H */
|