From: Paolo Abeni <pabeni@redhat.com>
To: Matthieu Baerts <matthieu.baerts@tessares.net>,
MPTCP Upstream <mptcp@lists.01.org>
Subject: [MPTCP] Re: [Weekly meetings] MoM - 18th of March 2021
Date: Fri, 19 Mar 2021 11:59:11 +0100 [thread overview]
Message-ID: <fe87c0aa901db6734f43c0bfac8e931ca55b048c.camel@redhat.com> (raw)
In-Reply-To: <3781fd70-ab60-529b-a877-adc0b41c87fb@tessares.net>
Hello,
I'm sorry for skipping this mtg.
On Thu, 2021-03-18 at 18:22 +0100, Matthieu Baerts wrote:
> Patches to send to netdev:
> - net:
> - nothing to send
>
> - net-next:
> - Maybe sockopt allowance list by Paolo?:
> - Or do we want to wait to have syzkaller exercising them more?
> - Or better to expose it to netdev ASAP?
> - *@Paolo* : what do you think? :)
I would wait a bit for the additional sockopt patches from Florian.
> sockopt allowance list:
> - What to do for -net and maybe stable branches?
> - Should we send the 3 patches to -net to have something close to
> net-next and ease future backports/maintenance?
> - Or only blacklist the MCast sockopts?
> - *@Paolo* : what do you think? :)
I would opt for the blacklist, more -net like.
> Netdev:
> - 0x15 next summer (July):
> https://netdevconf.info/0x15/submit-proposal.html
> - Might be a remote conf only
I hate remote conf :(
Cheers,
Paolo
_______________________________________________
mptcp mailing list -- mptcp@lists.01.org
To unsubscribe send an email to mptcp-leave@lists.01.org
prev parent reply other threads:[~2021-03-19 10:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 17:22 [MPTCP] [Weekly meetings] MoM - 18th of March 2021 Matthieu Baerts
2021-03-19 10:59 ` Paolo Abeni [this message]
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=fe87c0aa901db6734f43c0bfac8e931ca55b048c.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=matthieu.baerts@tessares.net \
--cc=mptcp@lists.01.org \
/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.