summaryrefslogtreecommitdiff
path: root/drivers/media/rc/keymaps/rc-avermedia-a16d.c
diff options
context:
space:
mode:
authorArnd Bergmann <arnd@arndb.de>2019-06-17 14:16:52 +0300
committerMauro Carvalho Chehab <mchehab+samsung@kernel.org>2019-06-27 14:24:12 +0300
commit15a98fb2fc287bbfe430e854d56dcfc86eae21db (patch)
treeec09dc1c18646161b162fbee85addb09db93c359 /drivers/media/rc/keymaps/rc-avermedia-a16d.c
parenta91418ac130d1abff38e86ba6f5cbf19a5daacec (diff)
downloadlinux-15a98fb2fc287bbfe430e854d56dcfc86eae21db.tar.xz
media: dvb_frontend: split dvb_frontend_handle_ioctl function
Over time, dvb_frontend_handle_ioctl() has grown to the point where we now get a warning from the compiler about excessive stack usage: drivers/media/dvb-core/dvb_frontend.c: In function 'dvb_frontend_handle_ioctl': drivers/media/dvb-core/dvb_frontend.c:2692:1: error: the frame size of 1048 bytes is larger than 1024 bytes [-Werror=frame-larger-than=] Almost all of this is used by the dtv_frontend_properties structure in the FE_GET_PROPERTY and FE_GET_FRONTEND commands. Splitting those into separate function reduces the stack usage of the main function to just 136 bytes, the others are under 500 each. Signed-off-by: Arnd Bergmann <arnd@arndb.de> Signed-off-by: Sean Young <sean@mess.org> Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Diffstat (limited to 'drivers/media/rc/keymaps/rc-avermedia-a16d.c')
0 files changed, 0 insertions, 0 deletions