netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: saeedm@mellanox.com
Cc: netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
	leonro@mellanox.com, jgg@mellanox.com, dledford@redhat.com
Subject: Re: [PATCH mlx5-next 0/6] Mellanox, mlx5 next updates 2018-08-09
Date: Wed, 08 Aug 2018 19:37:02 -0700 (PDT)	[thread overview]
Message-ID: <20180808.193702.960669524487101933.davem@davemloft.net> (raw)
In-Reply-To: <20180808232353.15514-1-saeedm@mellanox.com>

From: Saeed Mahameed <saeedm@mellanox.com>
Date: Wed,  8 Aug 2018 16:23:47 -0700

> This series includes mlx5 core driver updates and mostly simple
> cleanups.
> 
> From Denis: Use max #EQs reported by firmware to request MSIX vectors.
> 
> From Eli: Trivial cleanups, unused arguments/functions and reduce
> command polling interval when command interface is in polling mode.
> 
> From Eran: Rename vport state enums, to better reflect their actual
> usage.

Series applied to net-next, thank you.

      parent reply	other threads:[~2018-08-09  4:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-08 23:23 [PATCH mlx5-next 0/6] Mellanox, mlx5 next updates 2018-08-09 Saeed Mahameed
2018-08-08 23:23 ` [PATCH mlx5-next 1/6] net/mlx5: Use max_num_eqs for calculation of required MSIX vectors Saeed Mahameed
2018-08-08 23:23 ` [PATCH mlx5-next 2/6] net/mlx5: Rename modify/query_vport state related enums Saeed Mahameed
2018-08-08 23:23 ` [PATCH mlx5-next 3/6] net/mlx5: E-Switch, Remove unused argument when creating legacy FDB Saeed Mahameed
2018-08-08 23:23 ` [PATCH mlx5-next 4/6] net/mlx5: Remove unused mlx5_query_vport_admin_state Saeed Mahameed
2018-08-08 23:23 ` [PATCH mlx5-next 5/6] net/mlx5: Unexport functions that need not be exported Saeed Mahameed
2018-08-09  4:34   ` Leon Romanovsky
2018-08-08 23:23 ` [PATCH mlx5-next 6/6] net/mlx5: Reduce command polling interval Saeed Mahameed
2018-08-09  2:37 ` 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=20180808.193702.960669524487101933.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=dledford@redhat.com \
    --cc=jgg@mellanox.com \
    --cc=leonro@mellanox.com \
    --cc=linux-rdma@vger.kernel.org \
    --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).