diff options
| author | Masahiro Yamada <yamada.masahiro@socionext.com> | 2019-01-03 10:10:38 +0900 |
|---|---|---|
| committer | Masahiro Yamada <yamada.masahiro@socionext.com> | 2019-01-06 09:46:51 +0900 |
| commit | 919987318a129b4d0c2203a3c6fd2d804be77100 (patch) | |
| tree | e072c3709d30b9383ada73673ef9ee4dcc79e9c1 /drivers | |
| parent | d4ce5458ea1b7d8ca49c436d602095c4912777d3 (diff) | |
| download | linux-919987318a129b4d0c2203a3c6fd2d804be77100.tar.bz2 | |
kbuild: generate asm-generic wrappers if mandatory headers are missing
Some time ago, Sam pointed out a certain degree of overwrap between
generic-y and mandatory-y. (https://lkml.org/lkml/2017/7/10/121)
I tweaked the meaning of mandatory-y a little bit; now it defines the
minimum set of ASM headers that all architectures must have.
If arch does not have specific implementation of a mandatory header,
Kbuild will let it fallback to the asm-generic one by automatically
generating a wrapper. This will allow to drop lots of redundant
generic-y defines.
Previously, "mandatory" was used in the context of UAPI, but I guess
this can be extended to kernel space ASM headers.
Suggested-by: Sam Ravnborg <sam@ravnborg.org>
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Acked-by: Sam Ravnborg <sam@ravnborg.org>
Diffstat (limited to 'drivers')
0 files changed, 0 insertions, 0 deletions