* [PATCH] vt: Fix comments to not refer to kill_proc
@ 2006-12-11 13:05 Eric W. Biederman
0 siblings, 0 replies; only message in thread
From: Eric W. Biederman @ 2006-12-11 13:05 UTC (permalink / raw)
To: Andrew Morton; +Cc: Linux Containers, linux-kernel
The code has been fixed to use kill_pid instead of kill_proc
fix the comments as well.
Signed-off-by: Eric W. Biederman <ebiederm@xmission.com>
---
drivers/char/vt_ioctl.c | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/char/vt_ioctl.c b/drivers/char/vt_ioctl.c
index ac5d60e..311493e 100644
--- a/drivers/char/vt_ioctl.c
+++ b/drivers/char/vt_ioctl.c
@@ -1087,7 +1087,7 @@ static void complete_change_console(struct vc_data *vc)
switch_screen(vc);
/*
- * This can't appear below a successful kill_proc(). If it did,
+ * This can't appear below a successful kill_pid(). If it did,
* then the *blank_screen operation could occur while X, having
* received acqsig, is waking up on another processor. This
* condition can lead to overlapping accesses to the VGA range
@@ -1110,7 +1110,7 @@ static void complete_change_console(struct vc_data *vc)
*/
if (vc->vt_mode.mode == VT_PROCESS) {
/*
- * Send the signal as privileged - kill_proc() will
+ * Send the signal as privileged - kill_pid() will
* tell us if the process has gone or something else
* is awry
*/
@@ -1170,7 +1170,7 @@ void change_console(struct vc_data *new_vc)
vc = vc_cons[fg_console].d;
if (vc->vt_mode.mode == VT_PROCESS) {
/*
- * Send the signal as privileged - kill_proc() will
+ * Send the signal as privileged - kill_pid() will
* tell us if the process has gone or something else
* is awry
*/
--
1.4.4.1.g278f
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2006-12-11 13:05 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2006-12-11 13:05 [PATCH] vt: Fix comments to not refer to kill_proc Eric W. Biederman
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®