From: Cong Ding <dinggnu@gmail.com>
To: Ralf Baechle <ralf@linux-mips.org>,
David Howells <dhowells@redhat.com>,
linux-mips@linux-mips.org, linux-kernel@vger.kernel.org
Cc: Cong Ding <dinggnu@gmail.com>
Subject: [PATCH] mips: kernel/vpe.c: fix wrong KERN_WARNING message
Date: Mon, 14 Jan 2013 17:23:29 +0000 [thread overview]
Message-ID: <1358184212-30381-1-git-send-email-dinggnu@gmail.com> (raw)
in the printk, the variable t euqals to NULL, so there is no t->index, we use
v->tc->index instead.
Signed-off-by: Cong Ding <dinggnu@gmail.com>
---
arch/mips/kernel/vpe.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/mips/kernel/vpe.c b/arch/mips/kernel/vpe.c
index eec690a..3e20c33 100644
--- a/arch/mips/kernel/vpe.c
+++ b/arch/mips/kernel/vpe.c
@@ -705,7 +705,7 @@ static int vpe_run(struct vpe * v)
printk(KERN_WARNING
"VPE loader: TC %d is already in use.\n",
- t->index);
+ v->tc->index);
return -ENOEXEC;
}
} else {
--
1.7.9.5
next reply other threads:[~2013-01-14 17:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-14 17:23 Cong Ding [this message]
2013-01-16 10:30 ` [PATCH] mips: kernel/vpe.c: fix wrong KERN_WARNING message Ralf Baechle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1358184212-30381-1-git-send-email-dinggnu@gmail.com \
--to=dinggnu@gmail.com \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.