From: Shmulik Ladkani <shmulik.ladkani@gmail.com>
To: Lance Richardson <lrichard@redhat.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net] ipv4: update comment to document GSO fragmentation cases.
Date: Fri, 4 Nov 2016 23:02:08 +0200 [thread overview]
Message-ID: <20161104230208.4eaa7346@halley> (raw)
In-Reply-To: <1478276558-10974-1-git-send-email-lrichard@redhat.com>
Hi,
On Fri, 4 Nov 2016 12:22:38 -0400 Lance Richardson <lrichard@redhat.com> wrote:
> This is a follow-up to commit eb96202f1e34 ("ipv4: allow local
> fragmentation in ip_finish_output_gso()"), updating the comment
> documenting cases in which fragmentation is needed for egress
> GSO packets.
>
> Suggested-by: Shmulik Ladkani <shmulik.ladkani@gmail.com>
> Signed-off-by: Lance Richardson <lrichard@redhat.com>
Thanks Lance.
Reviewed-by: Shmulik Ladkani <shmulik.ladkani@gmail.com>
next prev parent reply other threads:[~2016-11-04 21:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-04 16:22 [PATCH net] ipv4: update comment to document GSO fragmentation cases Lance Richardson
2016-11-04 21:02 ` Shmulik Ladkani [this message]
2016-11-09 17:46 ` David Miller
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=20161104230208.4eaa7346@halley \
--to=shmulik.ladkani@gmail.com \
--cc=lrichard@redhat.com \
--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).