From: fklassen at appneta.com (Fred Klassen)
Subject: [PATCH net v2 0/1] Allow TX timestamp with UDP GSO
Date: Sun, 26 May 2019 08:33:56 -0700 [thread overview]
Message-ID: <20190526153357.82293-1-fklassen@appneta.com> (raw)
Fixes an issue where TX Timestamps are not arriving on the error queue
when UDP_SEGMENT CMSG type is combined with CMSG type SO_TIMESTAMPING.
This is version 2 which moves the tests to net-next.
Fred Klassen (1):
net/udp_gso: Allow TX timestamp with UDP GSO
net/ipv4/udp_offload.c | 4 ++++
1 file changed, 4 insertions(+)
--
2.11.0
WARNING: multiple messages have this Message-ID (diff)
From: fklassen@appneta.com (Fred Klassen)
Subject: [PATCH net v2 0/1] Allow TX timestamp with UDP GSO
Date: Sun, 26 May 2019 08:33:56 -0700 [thread overview]
Message-ID: <20190526153357.82293-1-fklassen@appneta.com> (raw)
Message-ID: <20190526153356.GmN_ivyO9STEwnGyiTAHy1OvNxQ2Ig021vrJ4JcIht8@z> (raw)
Fixes an issue where TX Timestamps are not arriving on the error queue
when UDP_SEGMENT CMSG type is combined with CMSG type SO_TIMESTAMPING.
This is version 2 which moves the tests to net-next.
Fred Klassen (1):
net/udp_gso: Allow TX timestamp with UDP GSO
net/ipv4/udp_offload.c | 4 ++++
1 file changed, 4 insertions(+)
--
2.11.0
next reply other threads:[~2019-05-26 15:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-26 15:33 fklassen [this message]
2019-05-26 15:33 ` [PATCH net v2 0/1] Allow TX timestamp with UDP GSO Fred Klassen
2019-05-26 15:33 ` [PATCH net v2 1/1] net/udp_gso: " fklassen
2019-05-26 15:33 ` Fred Klassen
2019-05-27 1:39 ` willemdebruijn.kernel
2019-05-27 1:39 ` Willem de Bruijn
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=20190526153357.82293-1-fklassen@appneta.com \
--to=linux-kselftest@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