netdev - Re: Question about Patch Submissions

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]

Date:	Wed, 19 Nov 2014 16:29:24 -0500
From:	rapier <rapier@....edu>
To:	Alexei Starovoitov <alexei.starovoitov@...il.com>
CC:	Cong Wang <cwang@...pensource.com>, netdev <netdev@...r.kernel.org>
Subject: Re: Question about Patch Submissions

On 11/18/14, 8:38 PM, Alexei Starovoitov wrote:
> On Tue, Nov 18, 2014 at 12:39 PM, rapier <rapier@....edu> wrote:
>> break this down for presentation. We can make sure each section of the patch
>> applies cleanly but the entirety of the patch set would have to be applied
>> for it to compile.
>
> all patches need to compile cleanly on all architectures,
> otherwise bisect will be broken.

The issue is that this is large patch set. The diff comes in at around 
2200 lines and adds new functionality to the kernel by implementing RFC 
4898. What I'm really trying to figure out is how to split up the diff 
files so I'm not dropping all 2200 lines into a single email message. 
I'm assuming that's not really how people want to see submissions but if 
I am incorrect please let me know.

There are two major components that we should be able to submit as 
distinct patches so that should reduce the line count per submission.

Chris Rapier

--
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