From: rapier <rapier@psc.edu>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Cong Wang <cwang@twopensource.com>, netdev <netdev@vger.kernel.org>
Subject: Re: Question about Patch Submissions
Date: Wed, 19 Nov 2014 16:29:24 -0500 [thread overview]
Message-ID: <546D0BB4.4030409@psc.edu> (raw)
In-Reply-To: <CAADnVQ+1_Ct3hhmZrCqpxcT=-XS4OXrpRbrHHHyOKQOuoDc06g@mail.gmail.com>
On 11/18/14, 8:38 PM, Alexei Starovoitov wrote:
> On Tue, Nov 18, 2014 at 12:39 PM, rapier <rapier@psc.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
prev parent reply other threads:[~2014-11-19 21:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-18 19:13 Question about Patch Submissions rapier
2014-11-18 20:21 ` Cong Wang
2014-11-18 20:39 ` rapier
2014-11-19 1:38 ` Alexei Starovoitov
2014-11-19 21:29 ` rapier [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=546D0BB4.4030409@psc.edu \
--to=rapier@psc.edu \
--cc=alexei.starovoitov@gmail.com \
--cc=cwang@twopensource.com \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).