From: Jakub Kicinski <kuba@kernel.org>
To: Jon Maloy <jmaloy@redhat.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, passt-dev@passt.top,
sbrivio@redhat.com, lvivier@redhat.com, dgibson@redhat.com,
eric.dumazet@gmail.com, edumazet@google.com
Subject: Re: [net-next, v2 2/2] selftests: add selftest for tcp SO_PEEK_OFF support
Date: Wed, 28 Aug 2024 10:43:01 -0700 [thread overview]
Message-ID: <20240828104301.3bc69271@kernel.org> (raw)
In-Reply-To: <d47f131f-2bb4-4581-a3cf-ecc2d4e215e9@redhat.com>
On Wed, 28 Aug 2024 12:24:48 -0400 Jon Maloy wrote:
> On 2024-08-27 17:50, Jakub Kicinski wrote:
> > On Mon, 26 Aug 2024 15:49:32 -0400 jmaloy@redhat.com wrote:
> >> +}
> >> +
> Does this require a re-posting?
Yes, as indicated by patchwork status of the series.
> > nit: extra new line at the end here, git warns when applying
> >
> > BTW did someone point out v6 is missing on the list? If so could
> > we add a Link: to that thread?
>
> I don't understand this question. v6 of what?
The Internet Protocol? :)
Rephrased:
Did someone point out on the mailing list that the support for
.set_peek_off is missing for TCPv6? If so could you add a Link:
tag pointing to that thread?
prev parent reply other threads:[~2024-08-28 17:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-26 19:49 [net-next, v2 0/2] Adding SO_PEEK_OFF for TCPv6 jmaloy
2024-08-26 19:49 ` [net-next, v2 1/2] tcp: add SO_PEEK_OFF socket option tor TCPv6 jmaloy
2024-08-27 0:30 ` Jason Xing
2024-08-26 19:49 ` [net-next, v2 2/2] selftests: add selftest for tcp SO_PEEK_OFF support jmaloy
2024-08-27 0:19 ` Jason Xing
2024-08-27 21:50 ` Jakub Kicinski
2024-08-28 16:24 ` Jon Maloy
2024-08-28 17:43 ` Jakub Kicinski [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=20240828104301.3bc69271@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=dgibson@redhat.com \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=jmaloy@redhat.com \
--cc=lvivier@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=passt-dev@passt.top \
--cc=sbrivio@redhat.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.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
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 IMAP folder(s).