All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@vyatta.com>
To: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Cc: shemminger@linux-foundation.org,
	Greg Rose <gregory.v.rose@intel.com>,
	netdev@vger.kernel.org, gospo@redhat.com, sassmann@redhat.com
Subject: Re: [iproute2] iproute2: Add VF spoofchk command description to ip-link.8 man page
Date: Thu, 9 Feb 2012 15:03:11 -0800	[thread overview]
Message-ID: <20120209150311.0f54a32e@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <1328822476-3405-1-git-send-email-jeffrey.t.kirsher@intel.com>

On Thu,  9 Feb 2012 13:21:16 -0800
Jeff Kirsher <jeffrey.t.kirsher@intel.com> wrote:

> From: Greg Rose <gregory.v.rose@intel.com>
> 
> Add documentation for the ip link set spoof checking option.  The
> expanded text section explaining the VF commands was missing this
> text.
> 
> Signed-off-by: Greg Rose <gregory.v.rose@intel.com>
> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
> ---
>  man/man8/ip-link.8 |    4 ++++
>  1 files changed, 4 insertions(+), 0 deletions(-)
> 
> diff --git a/man/man8/ip-link.8 b/man/man8/ip-link.8
> index e1eb948..8c63584 100644
> --- a/man/man8/ip-link.8
> +++ b/man/man8/ip-link.8
> @@ -301,6 +301,10 @@ as 0 disables VLAN tagging and filtering for the VF.
>  Setting this parameter to 0 disables rate limiting. The
>  .B vf
>  parameter must be specified.
> +
> +.sp
> +.BI spoofchk " on|off"
> +- turn packet spoof checking on or off for the specified VF.
>  .in -8
>  
>  .TP

Applied.

      reply	other threads:[~2012-02-09 23:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-09 21:21 [iproute2] iproute2: Add VF spoofchk command description to ip-link.8 man page Jeff Kirsher
2012-02-09 23:03 ` 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=20120209150311.0f54a32e@nehalam.linuxnetplumber.net \
    --to=shemminger@vyatta.com \
    --cc=gospo@redhat.com \
    --cc=gregory.v.rose@intel.com \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=sassmann@redhat.com \
    --cc=shemminger@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.