From: Saeed Mahameed <saeed@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>,
sridhar.samudrala@intel.com, edwin.peer@broadcom.com,
jacob.e.keller@intel.com
Cc: "David S. Miller" <davem@davemloft.net>,
Jason Gunthorpe <jgg@nvidia.com>,
netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
alexander.duyck@gmail.com, dsahern@kernel.org,
kiran.patil@intel.com, david.m.ertman@intel.com,
dan.j.williams@intel.com
Subject: Re: [pull request][net-next V10 00/14] Add mlx5 subfunction support
Date: Thu, 28 Jan 2021 16:03:02 -0800 [thread overview]
Message-ID: <d6fa72b34eb65e17847463bf7084f5a25c8ad492.camel@kernel.org> (raw)
In-Reply-To: <20210126173417.3123c8ea@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
On Tue, 2021-01-26 at 17:34 -0800, Jakub Kicinski wrote:
> On Fri, 22 Jan 2021 11:36:44 -0800 Saeed Mahameed wrote:
> > This series form Parav was the theme of this mlx5 release cycle,
> > we've been waiting anxiously for the auxbus infrastructure to make
> > it into
> > the kernel, and now as the auxbus is in and all the stars are
> > aligned, I
> > can finally submit this patchset of the devlink and mlx5
> > subfunction support.
> >
> > For more detailed information about subfunctions please see
> > detailed tag
> > log below.
>
> Are there any further comments, objections or actions that need to be
> taken on this series, anyone?
>
> Looks like the discussion has ended. Not knowing any users who would
> need this I'd like to at least make sure we have reasonable consensus
> among vendors.
Hey Jakub, sorry to nag, but I need to make some progress, can we move
on please ? my submission queue is about to explode :) !
Thanks,
Saeed.
next prev parent reply other threads:[~2021-01-29 0:04 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 19:36 [pull request][net-next V10 00/14] Add mlx5 subfunction support Saeed Mahameed
2021-01-22 19:36 ` [net-next V10 01/14] devlink: Prepare code to fill multiple port function attributes Saeed Mahameed
2021-01-29 1:40 ` patchwork-bot+netdevbpf
2021-01-22 19:36 ` [net-next V10 02/14] devlink: Introduce PCI SF port flavour and port attribute Saeed Mahameed
2021-01-22 19:36 ` [net-next V10 03/14] devlink: Support add and delete devlink port Saeed Mahameed
2021-01-22 19:36 ` [net-next V10 04/14] devlink: Support get and set state of port function Saeed Mahameed
2021-01-22 19:36 ` [net-next V10 05/14] net/mlx5: Introduce vhca state event notifier Saeed Mahameed
2021-01-22 19:36 ` [net-next V10 06/14] net/mlx5: SF, Add auxiliary device support Saeed Mahameed
2021-01-22 19:36 ` [net-next V10 07/14] net/mlx5: SF, Add auxiliary device driver Saeed Mahameed
2021-01-22 19:36 ` [net-next V10 08/14] net/mlx5: E-switch, Prepare eswitch to handle SF vport Saeed Mahameed
2021-01-22 19:36 ` [net-next V10 09/14] net/mlx5: E-switch, Add eswitch helpers for " Saeed Mahameed
2021-01-22 19:36 ` [net-next V10 10/14] net/mlx5: SF, Add port add delete functionality Saeed Mahameed
2021-01-22 19:36 ` [net-next V10 11/14] net/mlx5: SF, Port function state change support Saeed Mahameed
2021-01-22 19:36 ` [net-next V10 12/14] devlink: Add devlink port documentation Saeed Mahameed
2021-01-22 19:36 ` [net-next V10 13/14] devlink: Extend devlink port documentation for subfunctions Saeed Mahameed
2021-01-22 19:36 ` [net-next V10 14/14] net/mlx5: Add devlink subfunction port documentation Saeed Mahameed
2021-01-24 20:47 ` [pull request][net-next V10 00/14] Add mlx5 subfunction support Edwin Peer
2021-01-25 10:57 ` Parav Pandit
2021-01-25 13:22 ` Jason Gunthorpe
2021-01-25 19:23 ` Edwin Peer
2021-01-25 19:49 ` Jason Gunthorpe
2021-01-25 20:05 ` Edwin Peer
2021-01-25 20:22 ` Michael Chan
2021-01-25 20:26 ` Parav Pandit
2021-01-25 18:35 ` Edwin Peer
2021-01-25 19:34 ` Edwin Peer
2021-01-25 19:59 ` Jason Gunthorpe
2021-01-25 20:22 ` Edwin Peer
2021-01-25 20:41 ` Jason Gunthorpe
2021-01-25 21:23 ` Edwin Peer
2021-01-25 23:13 ` Jason Gunthorpe
2021-01-27 1:34 ` Jakub Kicinski
2021-01-29 0:03 ` Saeed Mahameed [this message]
2021-01-29 0:11 ` Jakub Kicinski
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=d6fa72b34eb65e17847463bf7084f5a25c8ad492.camel@kernel.org \
--to=saeed@kernel.org \
--cc=alexander.duyck@gmail.com \
--cc=dan.j.williams@intel.com \
--cc=davem@davemloft.net \
--cc=david.m.ertman@intel.com \
--cc=dsahern@kernel.org \
--cc=edwin.peer@broadcom.com \
--cc=jacob.e.keller@intel.com \
--cc=jgg@nvidia.com \
--cc=kiran.patil@intel.com \
--cc=kuba@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sridhar.samudrala@intel.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).