[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJ3xEMghu7ZB0YM8j_YJihpuNnDzOY2LU9-cTHwoWiBeYY7VPA@mail.gmail.com>
Date: Tue, 12 Apr 2016 00:17:32 +0300
From: Or Gerlitz <gerlitz.or@...il.com>
To: Saeed Mahameed <saeedm@...lanox.com>,
Matan Barak <matanb@...lanox.com>
Cc: Linux Netdev List <netdev@...r.kernel.org>,
"linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
"David S. Miller" <davem@...emloft.net>,
Doug Ledford <dledford@...hat.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Or Gerlitz <ogerlitz@...lanox.com>,
Leon Romanovsky <leonro@...lanox.com>,
Tal Alon <talal@...lanox.com>
Subject: Re: [PATCH for-next 2/2] net/mlx5: Update mlx5_ifc hardware features
On Mon, Apr 11, 2016 at 11:10 PM, Saeed Mahameed <saeedm@...lanox.com> wrote:
> Adding the needed mlx5_ifc hardware bits and structs
> for the following feature:
feature --> features
> * Add vport to steering commands for SRIOV ACL support
> * Add mlcr, pcmr and mcia registers for dump module EEPROM
> * Add support for FCS, baeacon led and disable_link bits to
> hca caps
> * Add CQE period mode bit in CQ context for CQE based CQ
> moderation support
> * Add umr SQ bit for fragmented memory registration
> * Add needed bits and caps for Striding RQ support
AFAIK, all the above are features will go through net-next, what made
you anticipate conflicts with linux-rdma?
Powered by blists - more mailing lists