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
Subject: Re: [PATCH 0/3] vt: add modifier support to cursor and navigation keys
Date: Tue, 10 Feb 2026 07:53:26 +0100 [thread overview]
Message-ID: <2026021006-reenact-suave-c86c@gregkh> (raw)
In-Reply-To: <q19s9nr3-6o47-4pq9-7r49-8q25p0021o1q@syhkavp.arg>
On Sun, Feb 08, 2026 at 11:22:27AM -0500, Nicolas Pitre wrote:
> On Sun, 8 Feb 2026, Greg Kroah-Hartman wrote:
>
> > Argh, sorry, I saw this patch series too late for this merge window.
> > I'll review it after -rc1 is out.
>
> Too bad.
>
> But please at least consider this one now
> https://lkml.org/lkml/2026/1/27/1886
> and queue it for the stable tree as well.
Sorry, that slipped through as well, I'll grab it after -rc1 is out and
get it backported to stable kernels.
thanks,
greg k-h
next prev parent reply other threads:[~2026-02-10 6:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 4:52 [PATCH 0/3] vt: add modifier support to cursor and navigation keys Nicolas Pitre
2026-02-03 4:52 ` [PATCH 1/3] vt: add modifier support to cursor keys Nicolas Pitre
2026-02-03 4:52 ` [PATCH 2/3] vt: add KT_CSI keysym type for modifier-aware CSI sequences Nicolas Pitre
2026-02-03 4:52 ` [PATCH 3/3] vt: add fallback to plain map for modifier-aware key types Nicolas Pitre
2026-02-08 15:28 ` [PATCH 0/3] vt: add modifier support to cursor and navigation keys Greg Kroah-Hartman
2026-02-08 16:22 ` Nicolas Pitre
2026-02-10 6:53 ` Greg Kroah-Hartman [this message]
2026-03-06 18:26 ` Nicolas Pitre
2026-03-12 13:48 ` Greg Kroah-Hartman
2026-03-12 18:56 ` Nicolas Pitre
2026-03-13 7:11 ` Greg Kroah-Hartman
2026-03-13 8:38 ` Greg Kroah-Hartman
2026-03-09 12:35 ` Alexey Gladkov
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=2026021006-reenact-suave-c86c@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=legion@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=nico@fluxnic.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.