From: "Remi Pommarel" <repk@triplefau.lt>
To: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
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: Wed, 12 Sep 2018 10:16:22 +0200 [thread overview]
Message-ID: <3459-5b98cb80-1-49ed5900@198591000> (raw)
In-Reply-To: <20180911184755.GA2562@kroah.com>
Hi,
On Tue, Sep 11, 2018 at 08:47:55PM +0200, Greg Kroah-Hartman wrote:
>
> 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?
I had used "RFC" here because I had one or two questions about the
implementation choices I made on those patches and not really on the
solution itself. So, yes, I don't mind sending another round of those
patches without RFC.
Thanks,
--
Remi
prev parent reply other threads:[~2018-09-12 8:16 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
2018-09-12 8:16 ` Remi Pommarel [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=3459-5b98cb80-1-49ed5900@198591000 \
--to=repk@triplefau.lt \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--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