diff options
author | Andy Shevchenko <andriy.shevchenko@linux.intel.com> | 2020-12-09 20:19:15 +0200 |
---|---|---|
committer | Richard Weinberger <richard@nod.at> | 2020-12-13 22:22:00 +0100 |
commit | 517f60206ee5d5f75c44bd9c8b1683d1d18a616a (patch) | |
tree | 3ca716b34deae010935418bfb61bad946a11cf42 /CREDITS | |
parent | f4ab7818ef7add1e10b33d8c3a4fe44858b7f6e9 (diff) | |
download | linux-stable-517f60206ee5d5f75c44bd9c8b1683d1d18a616a.tar.gz linux-stable-517f60206ee5d5f75c44bd9c8b1683d1d18a616a.tar.bz2 linux-stable-517f60206ee5d5f75c44bd9c8b1683d1d18a616a.zip |
um: Increase stack frame size threshold for signal.c
The signal.c can't use heap for bit data located on stack. However,
by default a compiler warns us about overstepping stack frame size
threshold:
arch/um/os-Linux/signal.c: In function ‘sig_handler_common’:
arch/um/os-Linux/signal.c:51:1: warning: the frame size of 2960 bytes is larger than 2048 bytes [-Wframe-larger-than=]
51 | }
| ^
arch/um/os-Linux/signal.c: In function ‘timer_real_alarm_handler’:
arch/um/os-Linux/signal.c:95:1: warning: the frame size of 2960 bytes is larger than 2048 bytes [-Wframe-larger-than=]
95 | }
| ^
Due to above increase stack frame size threshold explicitly for signal.c
to avoid unnecessary warning.
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Tested-by: David Gow <davidgow@google.com>
Signed-off-by: Richard Weinberger <richard@nod.at>
Diffstat (limited to 'CREDITS')
0 files changed, 0 insertions, 0 deletions