summaryrefslogtreecommitdiffstats
path: root/drivers/input
diff options
context:
space:
mode:
authorArnd Bergmann <arnd@arndb.de>2015-05-26 23:45:29 +0200
committerDmitry Torokhov <dmitry.torokhov@gmail.com>2015-06-02 19:43:47 +0200
commitffb6e0c9a0572f8e5f8e9337a1b40ac2ec1493a1 (patch)
tree046abcbc147037360407f0119300032d60f3681a /drivers/input
parentInput: synaptics_i2c - use proper boolean values (diff)
downloadlinux-ffb6e0c9a0572f8e5f8e9337a1b40ac2ec1493a1.tar.xz
linux-ffb6e0c9a0572f8e5f8e9337a1b40ac2ec1493a1.zip
tty: remove platform_sysrq_reset_seq
The platform_sysrq_reset_seq code was intended as a way for an embedded platform to provide its own sysrq sequence at compile time. After over two years, nobody has started using it in an upstream kernel, and the platforms that were interested in it have moved on to devicetree, which can be used to configure the sequence without requiring kernel changes. The method is also incompatible with the way that most architectures build support for multiple platforms into a single kernel. Now the code is producing warnings when built with gcc-5.1: drivers/tty/sysrq.c: In function 'sysrq_init': drivers/tty/sysrq.c:959:33: warning: array subscript is above array bounds [-Warray-bounds] key = platform_sysrq_reset_seq[i]; We could fix this, but it seems unlikely that it will ever be used, so let's just remove the code instead. We still have the option to pass the sequence either in DT, using the kernel command line, or using the /sys/module/sysrq/parameters/reset_seq file. Fixes: 154b7a489a ("Input: sysrq - allow specifying alternate reset sequence") Signed-off-by: Arnd Bergmann <arnd@arndb.de> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Diffstat (limited to 'drivers/input')
0 files changed, 0 insertions, 0 deletions