From: Raslan Darawsheh <rasland@nvidia.com>
To: Adham Masarwah <adham@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>,
Matan Azrad <matan@nvidia.com>, Idan Hackmon <idanhac@nvidia.com>,
Tamer Hleihel <tamerh@nvidia.com>,
Tal Shnaiderman <talshn@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>
Subject: RE: [PATCH 0/2] net/mlx5: support missing functionality for Windows
Date: Thu, 14 Apr 2022 07:39:25 +0000 [thread overview]
Message-ID: <BYAPR12MB3078D414470AAA3EB0440943CFEF9@BYAPR12MB3078.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20220410102955.66448-1-adham@nvidia.com>
Hi,
> -----Original Message-----
> From: Adham Masarwah <adham@nvidia.com>
> Sent: Sunday, April 10, 2022 1:30 PM
> To: dev@dpdk.org
> Cc: NBU-Contact-Thomas Monjalon (EXTERNAL) <thomas@monjalon.net>;
> Matan Azrad <matan@nvidia.com>; Idan Hackmon <idanhac@nvidia.com>;
> Tamer Hleihel <tamerh@nvidia.com>; Tal Shnaiderman
> <talshn@nvidia.com>; Slava Ovsiienko <viacheslavo@nvidia.com>
> Subject: [PATCH 0/2] net/mlx5: support missing functionality for Windows
>
> Adding support for set promiscuous modes and for MTU set/get
>
> Adham Masarwah (2):
> net/mlx5: add support for set promiscuous modes in Windows
> net/mlx5: add support for set and get MTU in Windows
>
> drivers/common/mlx5/windows/mlx5_glue.c | 86
> +++++++++++++++++++++++++++++++
> drivers/common/mlx5/windows/mlx5_glue.h | 8 +++
> drivers/net/mlx5/windows/mlx5_ethdev_os.c | 31 +++++++++--
> drivers/net/mlx5/windows/mlx5_os.c | 15 +++---
> 4 files changed, 127 insertions(+), 13 deletions(-)
>
> --
> 2.16.1.windows.4
Patch applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
next prev parent reply other threads:[~2022-04-14 7:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-10 10:29 Adham Masarwah
2022-04-14 7:39 ` Raslan Darawsheh [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-04-10 10:27 Adham Masarwah
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=BYAPR12MB3078D414470AAA3EB0440943CFEF9@BYAPR12MB3078.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=adham@nvidia.com \
--cc=dev@dpdk.org \
--cc=idanhac@nvidia.com \
--cc=matan@nvidia.com \
--cc=talshn@nvidia.com \
--cc=tamerh@nvidia.com \
--cc=thomas@monjalon.net \
--cc=viacheslavo@nvidia.com \
/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;
as well as URLs for NNTP newsgroup(s).