From: David Miller <davem@davemloft.net>
To: saeedm@mellanox.com
Cc: netdev@vger.kernel.org
Subject: Re: [pull request][net 0/6] Mellanox mlx5 fixes 2017-06-11
Date: Sun, 11 Jun 2017 16:42:10 -0400 (EDT) [thread overview]
Message-ID: <20170611.164210.726640838112020106.davem@davemloft.net> (raw)
In-Reply-To: <20170611140028.12467-1-saeedm@mellanox.com>
From: Saeed Mahameed <saeedm@mellanox.com>
Date: Sun, 11 Jun 2017 17:00:22 +0300
> This series contains some fixes for the mlx5 core and netdev driver.
>
> Please pull and let me know if there's any problem.
Pulled, thanks.
> For -stable:
> ("net/mlx5e: Added BW check for DIM decision mechanism") kernels >= 4.9
> ("net/mlx5e: Fix wrong indications in DIM due to counter wraparound") kernels >= 4.9
> ("net/mlx5: Remove several module events out of ethtool stats") kernels >= 4.10
> ("net/mlx5: Enable 4K UAR only when page size is bigger than 4K") kernels >= 4.11
>
> *all patches apply with no issue on their -stable.
>
> BTW I never asked you if this way of marking patches to -stable is good for you ?
> if you prefer another format please let me know.
It works fine for now, I'll let you know if it causes problems :)
prev parent reply other threads:[~2017-06-11 20:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-11 14:00 [pull request][net 0/6] Mellanox mlx5 fixes 2017-06-11 Saeed Mahameed
2017-06-11 14:00 ` [net 1/6] net/mlx5: Fix create vport flow table flow Saeed Mahameed
2017-06-11 14:00 ` [net 2/6] net/mlx5: Continue health polling until it is explicitly stopped Saeed Mahameed
2017-06-11 14:00 ` [net 3/6] net/mlx5: Remove several module events out of ethtool stats Saeed Mahameed
2017-06-11 14:00 ` [net 4/6] net/mlx5e: Added BW check for DIM decision mechanism Saeed Mahameed
2017-06-11 14:00 ` [net 5/6] net/mlx5e: Fix wrong indications in DIM due to counter wraparound Saeed Mahameed
2017-06-11 14:00 ` [net 6/6] net/mlx5: Enable 4K UAR only when page size is bigger than 4K Saeed Mahameed
2017-06-11 20:42 ` 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=20170611.164210.726640838112020106.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).