From: Daniel Thompson <daniel.thompson@linaro.org>
To: Jason Wessel <jason.wessel@windriver.com>
Cc: Daniel Thompson <daniel.thompson@linaro.org>,
kgdb-bugreport@lists.sourceforge.net,
linux-kernel@vger.kernel.org, patches@linaro.org
Subject: [PATCH 0/5] kdb: Cleanup code to read user input and handle escape sequences
Date: Fri, 31 Aug 2018 21:51:37 +0100 [thread overview]
Message-ID: <20180831205142.23609-1-daniel.thompson@linaro.org> (raw)
I spend a little time earlier this month looking at kdb_read() and ended
up doing a little light refactoring a bit to make easier to read.
Most of the patches are simple tidy ups although patches 4 and 5
introduce new behaviours. Patch 4 is probably not controversial
but perhaps patch 5 is ;-).
Tested as shown here:
https://github.com/daniel-thompson/kgdbtest/commit/c65e28d99357c2df6dac2cebe195574e634d04dc
Daniel Thompson (5):
kdb: Tidy up code to handle escape sequences
kdb: Simplify code to fetch characters from console
kdb: Remove special case logic from kdb_read()
kdb: Improve handling of characters from different input sources
kdb: Tweak escape handling for vi users
kernel/debug/kdb/kdb_io.c | 218 +++++++++++++++++---------------------
1 file changed, 99 insertions(+), 119 deletions(-)
--
2.17.1
next reply other threads:[~2018-08-31 20:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-31 20:51 Daniel Thompson [this message]
2018-08-31 20:51 ` [PATCH 1/5] kdb: Tidy up code to " Daniel Thompson
2018-08-31 20:51 ` [PATCH 2/5] kdb: Simplify code to fetch characters from console Daniel Thompson
2018-08-31 20:51 ` [PATCH 3/5] kdb: Remove special case logic from kdb_read() Daniel Thompson
2018-08-31 20:51 ` [PATCH 4/5] kdb: Improve handling of characters from different input sources Daniel Thompson
2018-08-31 20:51 ` [PATCH 5/5] kdb: Tweak escape handling for vi users Daniel Thompson
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=20180831205142.23609-1-daniel.thompson@linaro.org \
--to=daniel.thompson@linaro.org \
--cc=jason.wessel@windriver.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@linaro.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 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®