diff options
| author |   Arnd Bergmann <arnd@arndb.de> | 2014-09-26 21:34:58 +0200 |
|---|---|---|
| committer |   Ulf Hansson <ulf.hansson@linaro.org> | 2014-09-29 11:27:32 +0200 |
| commit | 5fef365b64b99d298d724b30b5c291b05d169f58 (patch) | |
| tree | aa76541b24dd4268bbf6a06fb1fa501f4ef7ccc2 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | mmc: rtsx_pci: Set power related cap2 macros (diff) | |
| download | wireguard-linux-5fef365b64b99d298d724b30b5c291b05d169f58.tar.xz wireguard-linux-5fef365b64b99d298d724b30b5c291b05d169f58.zip | |
mmc: atmel-mci: fix mismatched section on atmci_cleanup_slot
As of 528bc7808f4e ("mmc: atmel-mci: Release mmc resources on failure in probe"),
the atmci_probe() function calls atmci_cleanup_slot in the failure path.
This causes a new warning whenever the driver is built:
WARNING: drivers/mmc/host/built-in.o(.init.text+0xa04): Section mismatch in reference from the function atmci_probe() to the function .exit.text:atmci_cleanup_slot()
The function __init atmci_probe() references
a function __exit atmci_cleanup_slot().
Gcc correctly warns about this function getting dropped in the link stage
for the built-in case, which would cause undefined behavior when this error
path is hit. The solution is to simply drop the __exit annotation.
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Fixes: 528bc7808f4e ("mmc: atmel-mci: Release mmc resources on failure in probe")
Acked-by: Ludovic Desroches <ludovic.desroches@atmel.com>
Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>
Diffstat (limited to '')
0 files changed, 0 insertions, 0 deletions