From: Stephen Hemminger <stephen@networkplumber.org>
To: Solio Sarabia <solio.sarabia@intel.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH iproute2] iplink: validate maximum gso_max_size
Date: Thu, 14 Dec 2017 18:24:54 -0800 [thread overview]
Message-ID: <20171214182454.0eb101ce@xeon-e3> (raw)
In-Reply-To: <1513117522-5111-1-git-send-email-solio.sarabia@intel.com>
On Tue, 12 Dec 2017 14:25:22 -0800
Solio Sarabia <solio.sarabia@intel.com> wrote:
> Validate the upper limit for gso_max_size, valid range is [0-65,536]
> inclusive. Fix minor whitespace in iplink man page.
>
> Signed-off-by: Solio Sarabia <solio.sarabia@intel.com>
> ---
Applied to net-next
prev parent reply other threads:[~2017-12-15 2:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 22:25 [PATCH iproute2] iplink: validate maximum gso_max_size Solio Sarabia
2017-12-15 2:24 ` Stephen Hemminger [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=20171214182454.0eb101ce@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.org \
--cc=solio.sarabia@intel.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;
as well as URLs for NNTP newsgroup(s).