public inbox for dev@dpdk.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Kerem Aksu <kerem.aksu@i2i-systems.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH v3] cmdline: update clear screen behavior
Date: Mon, 9 Feb 2026 16:10:26 -0800	[thread overview]
Message-ID: <20260209161026.0dfed9e5@phoenix.local> (raw)
In-Reply-To: <20260116154256.206571-1-kerem.aksu@i2i-systems.com>

On Fri, 16 Jan 2026 18:42:56 +0300
Kerem Aksu <kerem.aksu@i2i-systems.com> wrote:

> Control+L should clear screen and redisplay prompt at the top
> line. DPDK rdline library will not change anything on the screen when
> fed with Control+L.  When prompt is lost after too many text written
> to the terminal, users will press Control+L to clear screen and put
> the prompt to the top line. This is expected behavior in bash(1) or
> applications that are using readline(3). Updated to behave as users
> expected.
> 
> Signed-off-by: Kerem Aksu <kerem.aksu@i2i-systems.com>
> ---
>  doc/guides/rel_notes/release_26_03.rst |  1 +
>  lib/cmdline/cmdline_rdline.c           | 29 ++++++++++++++++++++------
>  lib/cmdline/cmdline_vt100.h            |  1 +
>  3 files changed, 25 insertions(+), 6 deletions(-)

I was going to queue this to next-net.
But AI review sees some things that need to be addressed.
Do you want to resubmit with fixed release note, or I can fix that.


Errors: None.

Warnings:

    Release note entry is placed under "API Changes" but the public API signature is unchanged — this is a behavior change and may belong under a different section.
    Commit body could open with what the patch does rather than jumping into background.
    Pre-existing missing spaces around operators (i=0 ; i<rdl->prompt_size) in touched function — good opportunity to clean up.

Info:

    rdline_clear_screen() wrapper is only called once; could be inlined, but the named function improves readability at the call site. Fine either way.

Overall: Clean patch, good refactoring approach preserving the public API. No correctness issues.

  reply	other threads:[~2026-02-10  0:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-05 11:35 [PATCH] cmdline: update clear screen behavior Kerem Aksu
2026-01-05 15:07 ` Marat Khalili
2026-01-05 20:27   ` Kerem Aksu
2026-01-14 18:00 ` Stephen Hemminger
2026-01-16 15:42 ` [PATCH v3] " Kerem Aksu
2026-02-10  0:10   ` Stephen Hemminger [this message]
2026-02-12  0:23   ` Stephen Hemminger
2026-02-12  7:56     ` Kerem Aksu
2026-02-14 19:08   ` Stephen Hemminger

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=20260209161026.0dfed9e5@phoenix.local \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=kerem.aksu@i2i-systems.com \
    /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