diff options
| author | Paul Gortmaker <[email protected]> | 2015-06-03 20:03:56 -0400 |
|---|---|---|
| committer | Greg Kroah-Hartman <[email protected]> | 2015-06-08 13:46:43 -0700 |
| commit | fc368ea1ea00c9418d6f2c25cd4c0869f1a16d5f (patch) | |
| tree | a03cabfed40decf6640b1c7202bcb24ab7da965a /tools/perf/scripts/python/bin/stackcollapse-record | |
| parent | 5a6a7cd05c039f3c4d8f5f52fddfb7cb2bbd6119 (diff) | |
drivers/hwtracing: fix coresight-etm4x implicit <module.h> usage
In commit 2e1cdfe184b5202d51e0611d7a051e2bea303946 ("coresight-etm4x:
Adding CoreSight ETM4x driver") this driver was added.
It uses module_amba_driver() to register itself with the system,
which is just an alias for module_driver. This currently works by
relying on getting that via init.h but we are planning to move that
code[1] to module.h -- at which time this will fail to compile since
it does not include module.h currently, resulting in:
drivers/hwtracing/coresight/coresight-etm4x.c:2701:1: note: in expansion of macro ‘module_amba_driver’
module_amba_driver(etm4x_driver);
^
include/linux/device.h:1296:1: error: type defaults to ‘int’ in declaration of ‘module_init’ [-Werror=implicit-int]
module_init(__driver##_init); \
^
In the future, the amba support may want to create another alias that
uses builtin_driver[2] for cases like this which are using bool Kconfig
triggers, but for now we just fix the implicit include.
[1] https://lkml.kernel.org/r/[email protected]
[2] https://lkml.kernel.org/r/[email protected]
Cc: Pratik Patel <[email protected]>
Cc: Kaixu Xia <[email protected]>
Signed-off-by: Paul Gortmaker <[email protected]>
Acked-by: Mathieu Poirier <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-record')
0 files changed, 0 insertions, 0 deletions