summaryrefslogtreecommitdiff
path: root/fs/freevxfs
diff options
context:
space:
mode:
authorAlan Cox <alan@linux.intel.com>2012-04-24 11:06:06 +0100
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2012-04-24 16:14:14 -0700
commit5d1a33fa5573702394a4d09a9872f3f930c06d58 (patch)
tree1e1ad3fd38f2bd1ac0f375ac18e9471af2861ee2 /fs/freevxfs
parent10af77c193681398e5dbe830db181d86047fcd41 (diff)
downloadlinux-rt-5d1a33fa5573702394a4d09a9872f3f930c06d58.tar.gz
vt: push the tty_lock down into the map handling
When we do this it becomes clear the lock we should be holding is the vc lock, and in fact many of our other helpers are properly invoked this way. We don't at this point guarantee not to race the keyboard code but the results of that appear harmless and that was true before we started as well. We now have no users of tty_lock in the console driver... Signed-off-by: Alan Cox <alan@linux.intel.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'fs/freevxfs')
0 files changed, 0 insertions, 0 deletions