linux-kernel - Re: [PULL REQUEST] mux for 4.12

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: <ee447077-8fcb-4b8a-9f00-77c6bcb01030@axentia.se>
Date:   Mon, 27 Mar 2017 13:25:03 +0200
From:   Peter Rosin <peda@...ntia.se>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
CC:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PULL REQUEST] mux for 4.12

On 2017-03-27 11:49, Greg Kroah-Hartman wrote:
> On Mon, Mar 27, 2017 at 10:30:44AM +0200, Peter Rosin wrote:
>> Hi Greg,
>>
>> Today seemed like a good day to send you the pull request for the new mux
>> controller subsystem. I hope the details are ok. If not, let me know and
>> I'll try to rework it. I also included some text for the merge commit, if
>> you want/need it:
> 
> Can you please just send me patches, so that people cna review them,
> including myself?  I only pull from a very small group of people, and
> only from kernel.org accounts.  Brand new subsystems need to be sent as
> patches, sorry.
> 
> Have all of the needed subsystem maintainers signed off on these patches
> already as well?

Yup, the appropriate tags are there IIUC, and the patches has been sent a
number of times for review. Last time was a couple of weeks ago [1], but now
that I look closer, I seem to have failed to Cc: you at the time. I'll send
a v11 though, so please don't pick v10. I made a couple of very minor fixups
since...

Cheers,
peda

[1] https://lkml.org/lkml/2017/3/10/411