All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Krystad <peter.krystad at linux.intel.com>
To: mptcp at lists.01.org
Subject: Re: [MPTCP] [PATCH MPTCP 0/2] mptcp: token api refactoring/cleanup
Date: Thu, 05 Sep 2019 10:25:04 -0700	[thread overview]
Message-ID: <57ad65189bf7d171641e71e936815f128e6f8b48.camel@linux.intel.com> (raw)
In-Reply-To: 20190902110909.3724-1-fw@strlen.de

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


On Mon, 2019-09-02 at 13:09 +0200, Florian Westphal wrote:
> I tried to fold the earlier 'RFC v2' in a way so that it allows
> easy squashing.
> 
> Patch #1 is the only one where this is painless.
> For all others, things are not easy because conflicts exist all
> over the place.
> 
> So I see two ways forward:
> 1. I rebase this myself and offer a pull request for the resulting series
> 2. Only squash the first patch and keep the rest as extra patch.
> 
> I suggest we go with #2.  The export tree already has a few patches
> that need to be squashed anyway before sending a formal series.
> 
This looks good and I'm fine with the extra patch for now, would just be too
hard to split this up and squash to all kinds of different places.

Peter.

> Also, the export branch is currently not bisectable, I get build
> errors mid-series.
> 
> I don't think this is a problem for now, I think it makes sense to
> not squash the larger patches for the time being.
> 
> Once another patch series is to be submitted to netdev, the export
> branch can be renamed/archived and a reorganisation can be done at that
> point (and the result diff'd versus the old export branch to make sure
> there is no difference in resulting code).
> 
> 
> _______________________________________________
> mptcp mailing list
> mptcp(a)lists.01.org
> https://lists.01.org/mailman/listinfo/mptcp


             reply	other threads:[~2019-09-05 17:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-05 17:25 Peter Krystad [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-09-07 15:56 [MPTCP] [PATCH MPTCP 0/2] mptcp: token api refactoring/cleanup Matthieu Baerts
2019-09-04 12:01 Florian Westphal
2019-09-04 11:53 Matthieu Baerts
2019-09-04 11:43 Florian Westphal
2019-09-04 11:16 Matthieu Baerts
2019-09-02 11:09 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=57ad65189bf7d171641e71e936815f128e6f8b48.camel@linux.intel.com \
    --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.