netdev - Re: [pull-request] mlx5-next branch 2021-12-15

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <2697f58ef720d6b8f9163ea1151a4daba7043e86.camel@kernel.org>
Date:   Wed, 15 Dec 2021 15:35:09 -0800
From:   Saeed Mahameed <saeed@...nel.org>
To:     Jakub Kicinski <kuba@...nel.org>
Cc:     Leon Romanovsky <leonro@...dia.com>,
        Jason Gunthorpe <jgg@...dia.com>,
        "davem@...emloft.net" <davem@...emloft.net>,
        "linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: [pull-request] mlx5-next branch 2021-12-15

On Wed, 2021-12-15 at 14:58 -0800, Jakub Kicinski wrote:
> On Wed, 15 Dec 2021 22:14:11 +0000 Saeed Mahameed wrote:
> > On Wed, 2021-12-15 at 11:23 -0800, Jakub Kicinski wrote:
> > > On Wed, 15 Dec 2021 10:49:45 -0800 Saeed Mahameed wrote:  
> > > > This pulls mlx5-next branch into net-next and rdma branches.
> > > > All patches already reviewed on both rdma and netdev mailing
> > > > lists.
> > > > 
> > > > Please pull and let me know if there's any problem.
> > > > 
> > > > 1) Add multiple FDB steering priorities [1]
> > > > 2) Introduce HW bits needed to configure MAC list size of
> > > > VF/SF.
> > > >    Required for ("net/mlx5: Memory optimizations") upcoming
> > > > series
> > > > [2].  
> > > 
> > > Why are you not posting the patches?  
> > 
> > already posted before :
> > [1]
> > https://lore.kernel.org/netdev/20211201193621.9129-1-saeed@kernel.org/
> > [2]
> > https://lore.kernel.org/lkml/20211208141722.13646-1-shayd@nvidia.com/
> 
> Post them as a reply to the pull request like you usually do, please.

They were already posted, and reviewed, and all maintainers were CC'ed,
including you, why do you want me to spam the mailing list over and
over again with the same patches ?  This is not how genuine pull
requests are supposed to work.