All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Westphal <fw at strlen.de>
To: mptcp at lists.01.org
Subject: [MPTCP] Re: [GIT] move TCP-related commits to the beginning
Date: Mon, 07 Oct 2019 17:00:59 +0200	[thread overview]
Message-ID: <20191007150059.GL13866@breakpoint.cc> (raw)
In-Reply-To: 7a9e06aa-4078-7d3d-9c64-ecf231dad17d@tessares.net

[-- Attachment #1: Type: text/plain, Size: 1337 bytes --]

Matthieu Baerts <matthieu.baerts(a)tessares.net> wrote:
> > ... this turns 'tcp: clean ext on tx recycle' into a one-line change.
> 
> Good idea! Just applied this diff and added your signed-off to the patch.

Thanks!

> > If we place this early in the series, then
> > 
> > > 966eb30045b9 mptcp: increment MIB counters in a few places
> > 
> > ... could be folded into the patches that add those code paths.
> > 
> > Perhaps right after 'mptcp: Add MPTCP socket stubs'?
> > 
> > Could also be squashed, I do not mind.  Just a suggestion.
> 
> For me it is clearer to have dedicated patches for the introduction of the
> MIBs: it might help reviewers to easily point out "strategic places" or
> because spending less time on that because it only modifies MPTCP code :)

Right, we can do this as a followup so it doesn't influence the initial
batch sizes in any way.

In light of this I agree its better to keep it as-is.

> It is just that I guess the reviewers will not like having too big patches
> neither. I understand that 40 patches is too big but as a reviewer, I would
> prefer having a very few more patches and split per features / refactoring.

Same here.

> I mean: if we send the same modifications in less patches, I don't know if
> it will help reviewers.

Right.  Lets keep it separate.

             reply	other threads:[~2019-10-07 15:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-07 15:00 Florian Westphal [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-10-08 12:27 [MPTCP] Re: [GIT] move TCP-related commits to the beginning Matthieu Baerts
2019-10-08 12:15 Florian Westphal
2019-10-08 11:41 Matthieu Baerts
2019-10-08  9:08 Matthieu Baerts
2019-10-07 22:54 Mat Martineau
2019-10-07 16:03 Matthieu Baerts
2019-10-07 15:23 Florian Westphal
2019-10-07 15:03 Matthieu Baerts
2019-10-07 14:45 Matthieu Baerts
2019-10-07 14:11 Florian Westphal

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=20191007150059.GL13866@breakpoint.cc \
    --to=unknown@example.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.