[S390] locking problem with __cpcmd.

bf3dbdcd · Christian Borntraeger <[email protected]> · 2007-01-09 10:19:03 +01:00

Changeset 740b5706b9c4b3767f597b3ea76654c6f2a800b2 moved the protecting
spinlock from __cpcmd to cpcmd. Therefore vmcp can no longer use __cpcmd,
instead we have to use cpcmd.

Signed-off-by: Christian Borntraeger <[email protected]>
Signed-off-by: Martin Schwidefsky <[email protected]>

Commit: bf3dbdcd0bfca74c16ad0b2b5a978907c864ed4c
Parents: d8ad075e

Changes

1 files changed · +1 −1

File	Status	Add	Del	Content
drivers/s390/char/vmcp.c	modified	+1	−1	View file

drivers/s390/char/vmcp.c

View file

diff --git a/drivers/s390/char/vmcp.c b/drivers/s390/char/vmcp.c
index 1678b6c..a420cd0 100644
--- a/drivers/s390/char/vmcp.c
+++ b/drivers/s390/char/vmcp.c
@@ -117,7 +117,7 @@ vmcp_write(struct file *file, const char __user * buff, size_t count,
 		return -ENOMEM;
 	}
 	debug_text_event(vmcp_debug, 1, cmd);
-	session->resp_size = __cpcmd(cmd, session->response,
+	session->resp_size = cpcmd(cmd, session->response,
 				     session->bufsize,
 				     &session->resp_code);
 	up(&session->mutex);