All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mat Martineau <mathew.j.martineau at linux.intel.com>
To: mptcp at lists.01.org
Subject: [MPTCP] Re: Weekly meeting - 12 November 2020 16:00 UTC (8am PDT, 5pm CET, 12pm CST)
Date: Wed, 11 Nov 2020 16:21:24 -0800	[thread overview]
Message-ID: <7e83d1b1-4cf1-2a1f-15a4-cf7228c63db9@linux.intel.com> (raw)
In-Reply-To: 78a800944b5ffc88c1155def85866cb28bd327ad.camel@redhat.com

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

On Wed, 11 Nov 2020, Paolo Abeni wrote:

> On Wed, 2020-11-11 at 16:09 +0100, Matthieu Baerts wrote:
>> Hello everybody!
>>
>> Our public MPTCP upstreaming weekly web conference is scheduled for
>> tomorrow.
>>
>> The list of topics is available here:
>> https://annuel2.framapad.org/p/mptcp_upstreaming_20201112
>>
>> Feel free to add/modify topics!
>
> I'd like to post upstream the following patches:
>
> mptcp: send explicit ack on delayed ack_seq incr
> mptcp: keep track of advertised windows right edge
> mptcp: rework poll+nospace handling
> mptcp: try to push pending data on snd una updates
> mptcp: move page frag allocation in mptcp_sendmsg()
> mptcp: refactor shutdown and close
> mptcp: introduce MPTCP snd_nxt
> mptcp: add accounting for pending data
> mptcp: reduce the arguments of mptcp_sendmsg_frag
> mptcp: introduce mptcp_schedule_work
> tcp: factor out __tcp_close() helper
> mptcp: use tcp_build_frag()
> tcp: factor out tcp_build_frag()
>
> in a single series. My plan is let the self-tests run for while on net-
> next plus the above and then post (likely, tomorrow before the mtg).
>
> If there are objections or different opinions please let me know!

Sounds like a good plan, thanks Paolo.

--
Mat Martineau
Intel

             reply	other threads:[~2020-11-12  0:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-12  0:21 Mat Martineau [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-11-11 17:32 [MPTCP] Re: Weekly meeting - 12 November 2020 16:00 UTC (8am PDT, 5pm CET, 12pm CST) Paolo Abeni

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=7e83d1b1-4cf1-2a1f-15a4-cf7228c63db9@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.