From: David Miller <davem@davemloft.net>
To: saeedm@mellanox.com
Cc: netdev@vger.kernel.org
Subject: Re: [pull request][net 0/7] Mellanox, mlx5 fixes 2018-04-26
Date: Fri, 27 Apr 2018 14:32:35 -0400 (EDT) [thread overview]
Message-ID: <20180427.143235.2029595013206143045.davem@davemloft.net> (raw)
In-Reply-To: <20180426195842.29665-1-saeedm@mellanox.com>
From: Saeed Mahameed <saeedm@mellanox.com>
Date: Thu, 26 Apr 2018 12:58:35 -0700
> This pull request includes fixes for mlx5 core and netdev driver.
>
> Please pull and let me know if there's any problems.
Pulled.
> For -stable v4.12
> net/mlx5e: TX, Use correct counter in dma_map error flow
> For -stable v4.13
> net/mlx5: Avoid cleaning flow steering table twice during error flow
> For -stable v4.14
> net/mlx5e: Allow offloading ipv4 header re-write for icmp
> For -stable v4.15
> net/mlx5e: DCBNL fix min inline header size for dscp
> For -stable v4.16
> net/mlx5: Fix mlx5_get_vector_affinity function
Queued up for -stable, thanks.
prev parent reply other threads:[~2018-04-27 18:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-26 19:58 [pull request][net 0/7] Mellanox, mlx5 fixes 2018-04-26 Saeed Mahameed
2018-04-26 19:58 ` [net 1/7] net/mlx5e: Allow offloading ipv4 header re-write for icmp Saeed Mahameed
2018-04-26 19:58 ` [net 2/7] net/mlx5e: DCBNL fix min inline header size for dscp Saeed Mahameed
2018-04-26 19:58 ` [net 3/7] net/mlx5: Fix mlx5_get_vector_affinity function Saeed Mahameed
2018-04-26 19:58 ` [net 4/7] net/mlx5e: TX, Use correct counter in dma_map error flow Saeed Mahameed
2018-04-26 19:58 ` [net 5/7] net/mlx5: Avoid cleaning flow steering table twice during " Saeed Mahameed
2018-04-26 19:58 ` [net 6/7] net/mlx5e: Fix traffic between VF and representor Saeed Mahameed
2018-04-26 19:58 ` [net 7/7] net/mlx5: Properly deal with flow counters when deleting rules Saeed Mahameed
2018-04-27 18:32 ` 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=20180427.143235.2029595013206143045.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).