Re: [for-next V2 00/17][PULL request] Mellanox mlx5 core driver updates 2016-08-20

From: Saeed Mahameed Date: Mon, 22 Aug 2016 20:56:43 +0300 > Technical question though. Do i need to create a new tag for the new > pull request? I mean, should the tag always point to the "up to" patch > in the pull request? or can I just use the same tag for the new

Re: [for-next V2 00/17][PULL request] Mellanox mlx5 core driver updates 2016-08-20

On Mon, Aug 22, 2016 at 8:11 PM, David Miller wrote: > > Sorry, too many patches. > > Please keep your series to 10 to 15 patches maximum. > > Please do not push back on this, I made several other submitters do > the same exact thing over the past few days. Sure. Rules are

Re: [for-next V2 00/17][PULL request] Mellanox mlx5 core driver updates 2016-08-20

Sorry, too many patches. Please keep your series to 10 to 15 patches maximum. Please do not push back on this, I made several other submitters do the same exact thing over the past few days.

[for-next V2 00/17][PULL request] Mellanox mlx5 core driver updates 2016-08-20

Hi Dave and Doug, This series contains several low level and API updates for mlx5 core commands interface and mlx5_ifc.h to be shared as base code for net-next and rdma mlx5 4.9 submissions. >From Saeed, ten patches that refactors old layouts of firmware commands which were manually generated