From mboxrd@z Thu Jan  1 00:00:00 1970
Content-Type: multipart/mixed; boundary="===============7890851600757800078=="
MIME-Version: 1.0
From: Florian Westphal <fw at strlen.de>
To: mptcp at lists.01.org
Subject: [MPTCP] [PATCH MPTCP 0/2] mptcp: token api refactoring/cleanup
Date: Mon, 02 Sep 2019 13:09:07 +0200
Message-ID: <20190902110909.3724-1-fw@strlen.de>
X-Status: 
X-Keywords:                  
X-UID: 1781

--===============7890851600757800078==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

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.

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



--===============7890851600757800078==--