netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: rapier <rapier@psc.edu>
To: Cong Wang <cwang@twopensource.com>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: Question about Patch Submissions
Date: Tue, 18 Nov 2014 15:39:17 -0500	[thread overview]
Message-ID: <546BAE75.7080802@psc.edu> (raw)
In-Reply-To: <CAHA+R7P-G4P-AzTM248FqNEm=dcuQOB_fwdM0Us3gsQgSeY0UQ@mail.gmail.com>

Cong,

Thanks for the response.

It's a pretty extensive patch set and we're trying to make sure it makes 
sense in context. It touches quite a few files and they're mostly 
interdependent. That's why we're having problems trying to figure out 
how to 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.

Chris

On 11/18/14, 3:21 PM, Cong Wang wrote:
> On Tue, Nov 18, 2014 at 11:13 AM, rapier <rapier@psc.edu> wrote:
>> I've read the documentation I've been able to find on the patch submission
>> process. I was hoping to clarify one thing though. When submitting a patch
>> that spans multiple files and functions is it better to break the submission
>> down by function or by file?
>>
>
> It depends on what you change, if your patch is trivial, say just cleaning up
> whitespaces, or a big single patch doesn't harm review, it is okay not
> to split it.
> Otherwise, probably you need to split it logically, each of which needs to at
> least compile.
>

  reply	other threads:[~2014-11-18 20:39 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 [this message]
2014-11-19  1:38     ` Alexei Starovoitov
2014-11-19 21:29       ` rapier

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=546BAE75.7080802@psc.edu \
    --to=rapier@psc.edu \
    --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).