From: Saeed Mahameed <saeedm@mellanox.com>
To: Leon Romanovsky <leonro@mellanox.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Subject: Re: [PATCH mlx5-next 0/5] Mellanox, mlx5 next updates 2019-09-29
Date: Mon, 2 Sep 2019 06:45:16 +0000 [thread overview]
Message-ID: <bb7ef7672dc2ca50cb70338eb61743b7db035dce.camel@mellanox.com> (raw)
In-Reply-To: <20190829234151.9958-1-saeedm@mellanox.com>
On Thu, 2019-08-29 at 23:42 +0000, Saeed Mahameed wrote:
> Hi All,
>
> This series includes misc updates for mlx5-next shared branch
> required
> for upcoming software steering feature.
>
> 1) Alex adds HW bits and definitions required for SW steering
> 2) Ariel moves device memory management to mlx5_core (From mlx5_ib)
> 3) Maor, Cleanups and fixups for eswitch mode and RoCE
> 4) Mar, Set only stag for match untagged packets
>
> In case of no objection this series will be applied to mlx5-next
> branch
> and sent later as pull request to both rdma-next and net-next
> branches.
>
Applied to mlx5-next
Thanks,
Saeed
prev parent reply other threads:[~2019-09-02 6:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-29 23:42 [PATCH mlx5-next 0/5] Mellanox, mlx5 next updates 2019-09-29 Saeed Mahameed
2019-08-29 23:42 ` [PATCH mlx5-next 1/5] net/mlx5: Move device memory management to mlx5_core Saeed Mahameed
2019-08-29 23:42 ` [PATCH mlx5-next 2/5] net/mlx5: Add HW bits and definitions required for SW steering Saeed Mahameed
2019-08-29 23:42 ` [PATCH mlx5-next 3/5] net/mlx5: Avoid disabling RoCE when uninitialized Saeed Mahameed
2019-08-29 23:42 ` [PATCH mlx5-next 4/5] net/mlx5: Add stub for mlx5_eswitch_mode Saeed Mahameed
2019-08-29 23:42 ` [PATCH mlx5-next 5/5] net/mlx5: Set only stag for match untagged packets Saeed Mahameed
2019-09-02 6:45 ` 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=bb7ef7672dc2ca50cb70338eb61743b7db035dce.camel@mellanox.com \
--to=saeedm@mellanox.com \
--cc=leonro@mellanox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox