netdev - Re: Linux XIA - merge proposal

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 for Android: free password hash cracker in your pocket

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

Message-ID: <54F70210.5070900@digirati.com.br>
Date:	Wed, 04 Mar 2015 08:01:04 -0500
From:	Michel Machado <michel@...irati.com.br>
To:	Greg KH <gregkh@...uxfoundation.org>
CC:	Daniel Borkmann <daniel@...earbox.net>, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: Linux XIA - merge proposal

On 03/04/2015 12:49 AM, Greg KH wrote:
> On Tue, Mar 03, 2015 at 07:31:58PM -0500, Michel Machado wrote:
>> Hi Daniel,
>>
>>>> We're fine with clearly marking Linux XIA as being under staging
>>>> as well as helping to define this review process for network stacks.
>>>
>>> With regard to staging, the code there is usually horrible and I'm
>>> not sure anyone really looks there, that would mitigate the review
>>> problem to the time when you try to get it out from there, so I'm
>>> not sure it brings anything. ;)
>>
>>     I suggested staging as a way to incrementally review the code.
>
> Yet you failed to at least ask the maintainer of the staging portion of
> the kernel, if this is a valid use of staging, and his resources...
>
> Not nice :(
>
> greg k-h

Hi Greg,

    I am sorry for having not asked you. Given that the staging process 
doesn't include network stacks, I'd thought that the correct way to go 
would be to bring the discussion to netdev first. Please understand that 
I'm not gaming, I'm just following my best understanding of the 
documentation of how to submit code. I'm really in uncharted waters here 
since all my accepted patches are tiny.

    In addition, I intend to work on the feedback I get. I'm not 
planning to have the code upstream and run away.

[ ]'s
Michel Machado
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html