mptcp.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Mat Martineau <mathew.j.martineau@linux.intel.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
	matthieu.baerts@tessares.net, fw@strlen.de,
	mptcp@lists.linux.dev
Subject: Re: [PATCH net-next 0/7] mptcp: Add timestamp support
Date: Fri, 04 Jun 2021 21:20:04 +0000	[thread overview]
Message-ID: <162284160432.23356.2648510889334376322.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210603232433.260703-1-mathew.j.martineau@linux.intel.com>

Hello:

This series was applied to netdev/net-next.git (refs/heads/master):

On Thu,  3 Jun 2021 16:24:26 -0700 you wrote:
> Enable the SO_TIMESTAMP and SO_TIMESTAMPING socket options for MPTCP
> sockets and add receive path cmsg support for timestamps.
> 
> Patches 1, 2, and 5 expose existing sock and tcp helpers for timestamps
> (no new EXPORT_SYMBOLS()s).
> 
> Patch 3 propagates timestamp options to subflows.
> 
> [...]

Here is the summary with links:
  - [net-next,1/7] sock: expose so_timestamp options for mptcp
    https://git.kernel.org/netdev/net-next/c/371087aa476a
  - [net-next,2/7] sock: expose so_timestamping options for mptcp
    https://git.kernel.org/netdev/net-next/c/ced122d90f52
  - [net-next,3/7] mptcp: sockopt: propagate timestamp request to subflows
    https://git.kernel.org/netdev/net-next/c/9061f24bf82e
  - [net-next,4/7] mptcp: setsockopt: handle SOL_SOCKET in one place only
    https://git.kernel.org/netdev/net-next/c/7a009a70ff8a
  - [net-next,5/7] tcp: export timestamp helpers for mptcp
    https://git.kernel.org/netdev/net-next/c/892bfd3ded0e
  - [net-next,6/7] mptcp: receive path cmsg support
    https://git.kernel.org/netdev/net-next/c/b7f653b297a4
  - [net-next,7/7] selftests: mptcp_connect: add SO_TIMESTAMPNS cmsg support
    https://git.kernel.org/netdev/net-next/c/5e6af0a729b6

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2021-06-04 21:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-03 23:24 [PATCH net-next 0/7] mptcp: Add timestamp support Mat Martineau
2021-06-03 23:24 ` [PATCH net-next 1/7] sock: expose so_timestamp options for mptcp Mat Martineau
2021-06-03 23:24 ` [PATCH net-next 2/7] sock: expose so_timestamping " Mat Martineau
2021-06-03 23:24 ` [PATCH net-next 3/7] mptcp: sockopt: propagate timestamp request to subflows Mat Martineau
2021-06-03 23:24 ` [PATCH net-next 4/7] mptcp: setsockopt: handle SOL_SOCKET in one place only Mat Martineau
2021-06-03 23:24 ` [PATCH net-next 5/7] tcp: export timestamp helpers for mptcp Mat Martineau
2021-06-03 23:24 ` [PATCH net-next 6/7] mptcp: receive path cmsg support Mat Martineau
2021-06-03 23:24 ` [PATCH net-next 7/7] selftests: mptcp_connect: add SO_TIMESTAMPNS " Mat Martineau
2021-06-04 21:20 ` patchwork-bot+netdevbpf [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=162284160432.23356.2648510889334376322.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=fw@strlen.de \
    --cc=kuba@kernel.org \
    --cc=mathew.j.martineau@linux.intel.com \
    --cc=matthieu.baerts@tessares.net \
    --cc=mptcp@lists.linux.dev \
    --cc=netdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).