linux-kernel - Re: [RFC PATCH 0/4] Add specific vt input's key map

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <3459-5b98cb80-1-49ed5900@198591000>
Date:   Wed, 12 Sep 2018 10:16:22 +0200
From:   "Remi Pommarel" <repk@...plefau.lt>
To:     "Greg Kroah-Hartman" <gregkh@...uxfoundation.org>
Cc:     "Jiri Slaby" <jslaby@...e.com>, linux-kernel@...r.kernel.org,
        "Alexander Viro" <viro@...iv.linux.org.uk>,
        "Kees Cook" <keescook@...omium.org>,
        "Elie Roudninski" <xademax@...il.com>
Subject: Re: [RFC PATCH 0/4] Add 
 specific vt input's key map

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