From: Mat Martineau <mathew.j.martineau at linux.intel.com>
To: mptcp at lists.01.org
Subject: [MPTCP] Updated net-next merge
Date: Thu, 03 May 2018 15:27:20 -0700 [thread overview]
Message-ID: <alpine.OSX.2.21.1805031525010.23105@mjmartin-mac01.sea.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 279 bytes --]
Hello everyone -
I updated the master branch at
https://github.com/multipath-tcp/mptcp_net-next
There were no complicated merge conflicts this time, and just one minor
fixup commit.
I plan to merge with net-next about once a week.
--
Mat Martineau
Intel OTC
next reply other threads:[~2018-05-03 22:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-03 22:27 Mat Martineau [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-05-21 16:41 [MPTCP] Updated net-next merge Christoph Paasch
2018-05-19 0:10 Mat Martineau
2018-04-25 23:19 Mat Martineau
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=alpine.OSX.2.21.1805031525010.23105@mjmartin-mac01.sea.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.