Linux Serial subsystem development
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Nicolas Pitre <nico@fluxnic.net>
Cc: Jiri Slaby <jirislaby@kernel.org>,
	Alexey Gladkov <legion@kernel.org>,
	linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org, kbd@lists.linux.dev
Subject: Re: [PATCH] vt: fix spurious modifier in CSI/cursor key sequences
Date: Thu, 9 Jul 2026 21:20:35 +0200	[thread overview]
Message-ID: <2026070921-everglade-obligate-597c@gregkh> (raw)
In-Reply-To: <4ro94n6o-r585-9693-07op-6p196oo273no@syhkavp.arg>

On Thu, Jul 09, 2026 at 02:24:29PM -0400, Nicolas Pitre wrote:
> 
> Ping.
> 
> On Thu, 25 Jun 2026, Nicolas Pitre wrote:

Sorry, am still catching up on patches, hopefully will get through them
"all" tomorrow...

      reply	other threads:[~2026-07-09 19:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-26  2:48 [PATCH] vt: fix spurious modifier in CSI/cursor key sequences Nicolas Pitre
2026-07-09 18:24 ` Nicolas Pitre
2026-07-09 19:20   ` Greg Kroah-Hartman [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=2026070921-everglade-obligate-597c@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=jirislaby@kernel.org \
    --cc=kbd@lists.linux.dev \
    --cc=legion@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=nico@fluxnic.net \
    --cc=stable@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