kdb: Fix a prompt management bug when using | grep
authorDaniel Thompson <daniel.thompson@linaro.org>
Thu, 11 Sep 2014 08:58:29 +0000 (09:58 +0100)
committerJason Wessel <jason.wessel@windriver.com>
Thu, 19 Feb 2015 18:39:03 +0000 (12:39 -0600)
commitab08e464a2cd8242fdc6e4f87f3480808364a97a
treeea25e537cc004b8c110bc3b55cc146268c2bbcd9
parent5454388113938d9592d6a6d5424469014da4ee86
kdb: Fix a prompt management bug when using | grep

Currently when the "| grep" feature is used to filter the output of a
command then the prompt is not displayed for the subsequent command.
Likewise any characters typed by the user are also not echoed to the
display. This rather disconcerting problem eventually corrects itself
when the user presses Enter and the kdb_grepping_flag is cleared as
kdb_parse() tries to make sense of whatever they typed.

This patch resolves the problem by moving the clearing of this flag
from the middle of command processing to the beginning.

Signed-off-by: Daniel Thompson <daniel.thompson@linaro.org>
Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
kernel/debug/kdb/kdb_main.c