public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nir Lichtman <nir@lichtman.org>
To: Doug Anderson <dianders@chromium.org>
Cc: jason.wessel@windriver.com, danielt@kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kdb: utilize more readable control characters macro in kdb io
Date: Thu, 28 Nov 2024 20:16:36 +0000	[thread overview]
Message-ID: <20241128201636.GA370101@lichtman.org> (raw)
In-Reply-To: <CAD=FV=V6B9mAb-EQaK1K+pa4duzOGmz=dt4QUFVVGUbq7NnK3Q@mail.gmail.com>

On Wed, Nov 27, 2024 at 12:55:10PM -0800, Doug Anderson wrote:
> Hi,
> 
> On Thu, Nov 21, 2024 at 12:45 PM Nir Lichtman <nir@lichtman.org> wrote:
> >
> > @@ -267,7 +267,7 @@ static char *kdb_read(char *buffer, size_t bufsize)
> >         if (key != 9)
> 
> FWIW, the "9" above is better as CTRL_KEY('I').

Right, missed that will fix.

> 
> 
> > @@ -176,14 +174,16 @@ int kdb_get_kbd_char(void)
> >         case KT_LATIN:
> >                 switch (keychar) {
> >                 /* non-printable supported control characters */
> > -               case CTRL('A'): /* Home */
> > -               case CTRL('B'): /* Left */
> > -               case CTRL('D'): /* Del */
> > -               case CTRL('E'): /* End */
> > -               case CTRL('F'): /* Right */
> > -               case CTRL('I'): /* Tab */
> > -               case CTRL('N'): /* Down */
> > -               case CTRL('P'): /* Up */
> > +               case CTRL_KEY('A'): /* Home */
> > +               case CTRL_KEY('B'): /* Left */
> > +               case CTRL_KEY('D'): /* Del */
> > +               case CTRL_KEY('E'): /* End */
> > +               case CTRL_KEY('F'): /* Right */
> > +               case CTRL_KEY('I'): /* Tab */
> > +               case CTRL_KEY('K'):
> > +               case CTRL_KEY('N'): /* Down */
> > +               case CTRL_KEY('P'): /* Up */
> > +               case CTRL_KEY('U'):
> 
> You snuck in a functionality change (adding Ctrl-K and Ctrl-U) here
> that should be in a separate patch.
> 

Oops, those are left overs of something else I was trying to do, will remove.

> Otherwise this looks nice to me.

Thanks! Will send out a v2 with fixes shortly,
Nir

      reply	other threads:[~2024-11-28 20:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-21 20:45 [PATCH] kdb: utilize more readable control characters macro in kdb io Nir Lichtman
2024-11-27 20:55 ` Doug Anderson
2024-11-28 20:16   ` Nir Lichtman [this message]

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=20241128201636.GA370101@lichtman.org \
    --to=nir@lichtman.org \
    --cc=danielt@kernel.org \
    --cc=dianders@chromium.org \
    --cc=jason.wessel@windriver.com \
    --cc=linux-kernel@vger.kernel.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