From: David Miller <davem@davemloft.net>
To: saeedm@mellanox.com
Cc: netdev@vger.kernel.org
Subject: Re: [pull request][net V2 0/8] Mellanox mlx5 fixes 2017-01-27
Date: Mon, 30 Jan 2017 15:45:10 -0500 (EST) [thread overview]
Message-ID: <20170130.154510.732270360823338547.davem@davemloft.net> (raw)
In-Reply-To: <20170129214626.21977-1-saeedm@mellanox.com>
From: Saeed Mahameed <saeedm@mellanox.com>
Date: Sun, 29 Jan 2017 23:46:18 +0200
> This pull request includes some mlx5 fixes for net, please see details
> below.
>
> Please pull and let me know if there's any problem.
Pulled...
> For -stable:
> net/mlx5e: Modify TIRs hash only when it's needed
> net/mlx5e: Fix update of hash function/key via ethtool
And queued up for -stable, thank you.
prev parent reply other threads:[~2017-01-30 20:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-29 21:46 [pull request][net V2 0/8] Mellanox mlx5 fixes 2017-01-27 Saeed Mahameed
2017-01-29 21:46 ` [net V2 1/8] net/mlx5: Change ENOTSUPP to EOPNOTSUPP Saeed Mahameed
2017-01-29 21:46 ` [net V2 2/8] net/mlx5: Return EOPNOTSUPP when failing to get steering name-space Saeed Mahameed
2017-01-29 21:46 ` [net V2 3/8] net/mlx5: E-Switch, Err when retrieving steering name-space fails Saeed Mahameed
2017-01-29 21:46 ` [net V2 4/8] net/mlx5: E-Switch, Re-enable RoCE on mode change only after FDB destroy Saeed Mahameed
2017-01-29 21:46 ` [net V2 5/8] net/mlx5e: Support TC encapsulation offloads with upper devices Saeed Mahameed
2017-01-29 21:46 ` [net V2 6/8] net/mlx5e: Modify TIRs hash only when it's needed Saeed Mahameed
2017-01-29 21:46 ` [net V2 7/8] net/mlx5e: Fix update of hash function/key via ethtool Saeed Mahameed
2017-01-29 21:46 ` [net V2 8/8] net/mlx5e: Check ets capability before ets query FW command Saeed Mahameed
2017-01-30 20:45 ` David Miller [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=20170130.154510.732270360823338547.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=saeedm@mellanox.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).