From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Alejandro Colomar <alx.manpages@gmail.com>,
Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
linux-man@vger.kernel.org
Cc: pabeni@redhat.com, netdev@vger.kernel.org,
Willem de Bruijn <willemb@google.com>
Subject: Re: [PATCH manpages v2 1/2] udp.7: add UDP_SEGMENT
Date: Mon, 06 Mar 2023 08:40:12 -0500 [thread overview]
Message-ID: <6405ed3c64fee_b9a692088@willemb.c.googlers.com.notmuch> (raw)
In-Reply-To: <c78f6a59-dac4-e5ce-cef6-533ad0cdbcac@gmail.com>
Alejandro Colomar wrote:
>
>
> On 3/6/23 14:30, Alejandro Colomar wrote:
> > Hi Willem,
> >
> > On 3/2/23 16:48, Willem de Bruijn wrote:
> >> From: Willem de Bruijn <willemb@google.com>
> >>
> >> UDP_SEGMENT was added in commit bec1f6f69736
> >> ("udp: generate gso with UDP_SEGMENT")
> >>
> >> $ git describe --contains bec1f6f69736
> >> linux/v4.18-rc1~114^2~377^2~8
> >>
> >> Kernel source has example code in tools/testing/selftests/net/udpgso*
> >>
> >> Per https://www.kernel.org/doc/man-pages/patches.html,
> >> "Describe how you obtained the information in your patch":
> >> I am the author of the above commit and follow-ons.
> >>
> >> Signed-off-by: Willem de Bruijn <willemb@google.com>
> >>
> >
> > It doesn't apply. Can you please rebase on top of master?
>
> Oops, sorry, I tried to apply 1/2 twice, instead of 1/2 and 2/2 :-)
> Ignore that.
Great. Thanks for applying, and for fixing up the cmsg references, Alex.
prev parent reply other threads:[~2023-03-06 13:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 15:48 [PATCH manpages v2 1/2] udp.7: add UDP_SEGMENT Willem de Bruijn
2023-03-02 15:48 ` [PATCH manpages v2 2/2] udp.7: add UDP_GRO Willem de Bruijn
2023-03-06 11:12 ` Simon Horman
2023-03-06 13:37 ` Alejandro Colomar
2023-03-06 11:12 ` [PATCH manpages v2 1/2] udp.7: add UDP_SEGMENT Simon Horman
2023-03-06 13:29 ` Alejandro Colomar
2023-03-06 13:30 ` Alejandro Colomar
2023-03-06 13:31 ` Alejandro Colomar
2023-03-06 13:40 ` Willem de Bruijn [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=6405ed3c64fee_b9a692088@willemb.c.googlers.com.notmuch \
--to=willemdebruijn.kernel@gmail.com \
--cc=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemb@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox