drivers/tty: don't use the byte channel handle as a parameter in ehv_bytechan.c
authorTimur Tabi <timur@freescale.com>
Fri, 23 Sep 2011 01:33:13 +0000 (20:33 -0500)
committerGreg Kroah-Hartman <gregkh@suse.de>
Mon, 26 Sep 2011 23:38:43 +0000 (16:38 -0700)
commitfd01a7a1bf6722e32efa679f15507148784af1f7
tree728c61021accadca1d3fe42c8bb49131839abeae
parent9cfb5c05fee914cc65d4706801f6bc424082b5f5
drivers/tty: don't use the byte channel handle as a parameter in ehv_bytechan.c

The ePAPR hypervisor byte channel console driver only supports one byte
channel as a console, and the byte channel handle is stored in a global
variable.  It doesn't make any sense to pass that handle as a parameter
to the console functions, since these functions already have access to the
global variable.

Signed-off-by: Timur Tabi <timur@freescale.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
drivers/tty/ehv_bytechan.c