All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthieu Baerts <matthieu.baerts at tessares.net>
To: mptcp at lists.01.org
Subject: [MPTCP] Re: [GIT] move TCP-related commits to the beginning
Date: Tue, 08 Oct 2019 14:27:42 +0200	[thread overview]
Message-ID: <c14d000f-731d-5261-1f82-66a9d56b945f@tessares.net> (raw)
In-Reply-To: 20191008121534.GD25052@breakpoint.cc

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

Hi Florian,

On 08/10/2019 14:15, Florian Westphal wrote:
> Matthieu Baerts <matthieu.baerts(a)tessares.net> wrote:
>> Feel free to tell me I have to do any other modifications (e.g. expose
>> tcp_request_sock_ipv6_ops).
> 
> Are you done with your rebase work?

Yes, I don't have anything planned for the moment, waiting for orders :-)

> I'd like to propose another set of fixups to get rid
> of refcounting and the kbuild robot warnings reported with rfcv2.

I can help if needed, if you prefer to create patch at the end of the 
series and I "squash" them in TopGit.

> I don't want to start doing this while export is in flux.

Thank you for the notification!

Cheers,
Matt
-- 
Matthieu Baerts | R&D Engineer
matthieu.baerts(a)tessares.net
Tessares SA | Hybrid Access Solutions
www.tessares.net
1 Avenue Jean Monnet, 1348 Louvain-la-Neuve, Belgium

             reply	other threads:[~2019-10-08 12:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-08 12:27 Matthieu Baerts [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-10-08 12:15 [MPTCP] Re: [GIT] move TCP-related commits to the beginning 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 15:00 Florian Westphal
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=c14d000f-731d-5261-1f82-66a9d56b945f@tessares.net \
    --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.