From: Saeed Mahameed <saeedm@nvidia.com>
To: "kuba@kernel.org" <kuba@kernel.org>
Cc: Leon Romanovsky <leonro@nvidia.com>,
Jason Gunthorpe <jgg@nvidia.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [pull-request] mlx5-next branch 2021-12-15
Date: Wed, 15 Dec 2021 22:41:34 +0000 [thread overview]
Message-ID: <dc7e552eabbccd8aeca27f77c3e8783da9379823.camel@nvidia.com> (raw)
In-Reply-To: <20211215112319.44d7daea@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
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/
prev parent reply other threads:[~2021-12-15 22:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 18:49 [pull-request] mlx5-next branch 2021-12-15 Saeed Mahameed
2021-12-15 19:23 ` Jakub Kicinski
2021-12-15 22:14 ` Saeed Mahameed
2021-12-15 22:58 ` Jakub Kicinski
2021-12-15 23:35 ` Saeed Mahameed
2021-12-15 23:44 ` Jakub Kicinski
2021-12-16 0:55 ` Saeed Mahameed
2021-12-15 22:41 ` Saeed Mahameed [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=dc7e552eabbccd8aeca27f77c3e8783da9379823.camel@nvidia.com \
--to=saeedm@nvidia.com \
--cc=davem@davemloft.net \
--cc=jgg@nvidia.com \
--cc=kuba@kernel.org \
--cc=leonro@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.