netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Gal Pressman <galp@mellanox.com>
Cc: netdev@vger.kernel.org, David Ahern <dsa@cumulusnetworks.com>,
	Leon Romanovsky <leonro@mellanox.com>,
	Eran Ben Elisha <eranbe@mellanox.com>,
	Sucheta Chakraborty <sucheta.chakraborty@qlogic.com>
Subject: Re: [PATCH iproute2 0/3] Fixes for minimum/maximum VF rate API
Date: Wed, 17 Jan 2018 10:54:58 -0800	[thread overview]
Message-ID: <20180117105458.18f97b76@xeon-e3> (raw)
In-Reply-To: <1516110120-32132-1-git-send-email-galp@mellanox.com>

On Tue, 16 Jan 2018 15:41:57 +0200
Gal Pressman <galp@mellanox.com> wrote:

> Hi all,
> The following patches will fix some issues with the "new" VF rate API, and
> add some clarifications to the documentation.
> 
> Thanks,
> Gal
> 
> Gal Pressman (3):
>   iplink: Validate minimum tx rate is less than maximum tx rate
>   ipaddress: Make sure VF min/max rate API is supported before using it
>   man: Document the meaning of zero in min/max_tx_rate parameters
> 
>  ip/ipaddress.c        | 6 ++++++
>  ip/iplink.c           | 8 ++++++++
>  man/man8/ip-link.8.in | 2 ++
>  3 files changed, 16 insertions(+)
> 

Applied, thanks.

      parent reply	other threads:[~2018-01-17 18:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-16 13:41 [PATCH iproute2 0/3] Fixes for minimum/maximum VF rate API Gal Pressman
2018-01-16 13:41 ` [PATCH iproute2 1/3] iplink: Validate minimum tx rate is less than maximum tx rate Gal Pressman
2018-01-16 13:41 ` [PATCH iproute2 2/3] ipaddress: Make sure VF min/max rate API is supported before using it Gal Pressman
2018-01-16 13:42 ` [PATCH iproute2 3/3] man: Document the meaning of zero in min/max_tx_rate parameters Gal Pressman
2018-01-17 18:54 ` 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=20180117105458.18f97b76@xeon-e3 \
    --to=stephen@networkplumber.org \
    --cc=dsa@cumulusnetworks.com \
    --cc=eranbe@mellanox.com \
    --cc=galp@mellanox.com \
    --cc=leonro@mellanox.com \
    --cc=netdev@vger.kernel.org \
    --cc=sucheta.chakraborty@qlogic.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).