public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Remi Pommarel <repk@triplefau.lt>
Cc: Jiri Slaby <jslaby@suse.com>,
	linux-kernel@vger.kernel.org,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	Kees Cook <keescook@chromium.org>,
	Elie Roudninski <xademax@gmail.com>
Subject: Re: [RFC PATCH 0/4] Add specific vt input's key map
Date: Tue, 11 Sep 2018 20:47:55 +0200	[thread overview]
Message-ID: <20180911184755.GA2562@kroah.com> (raw)
In-Reply-To: <20180905172022.GA30233@voidbox.localdomain>

On Wed, Sep 05, 2018 at 07:20:23PM +0200, Remi Pommarel wrote:
> Hi,
> 
> Just a gentle ping.
> 
> Any comments on this patchset that adds a way to have multiple
> keyboards with different keymap on a VT would be nice.

Normally I do not review "RFC" patches as it implies the submitter does
not think they are a valid solution.  How about resending them as if you
think this is something ready to be merged?

thanks,

greg k-h

  reply	other threads:[~2018-09-11 18:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-22 21:50 [RFC PATCH 0/4] Add specific vt input's key map Remi Pommarel
2018-08-22 21:50 ` [RFC PATCH 1/4] drivers/tty/vt/keyboard.c: refactor getting/setting a keymap entry Remi Pommarel
2018-08-22 21:50 ` [RFC PATCH 2/4] drivers/tty/vt/keyboard.c: add keyboard config for each vt's input Remi Pommarel
2018-08-22 21:50 ` [RFC PATCH 3/4] drivers/tty/vt/keyboard.c: Make key_down[] bitmap input dependent Remi Pommarel
2018-08-22 21:50 ` [RFC PATCH 4/4] drivers/tty/vt: add ioctl to manage input specific keyboard configs Remi Pommarel
2018-09-05 17:20 ` [RFC PATCH 0/4] Add specific vt input's key map Remi Pommarel
2018-09-11 18:47   ` Greg Kroah-Hartman [this message]
2018-09-12  8:16     ` Remi Pommarel

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=20180911184755.GA2562@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=jslaby@suse.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=repk@triplefau.lt \
    --cc=viro@zeniv.linux.org.uk \
    --cc=xademax@gmail.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