From: Raslan Darawsheh <rasland@nvidia.com>
To: "NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>,
Adham Masarwah <adham@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Matan Azrad <matan@nvidia.com>,
Idan Hackmon <idanhac@nvidia.com>,
Tamer Hleihel <tamerh@nvidia.com>,
Tal Shnaiderman <talshn@nvidia.com>
Subject: RE: [PATCH] doc: update release notes for 22.07
Date: Sun, 17 Apr 2022 06:59:18 +0000 [thread overview]
Message-ID: <BYAPR12MB30781FBA667FD8111A2A9FEFCFF09@BYAPR12MB3078.namprd12.prod.outlook.com> (raw)
In-Reply-To: <2100824.GUh0CODmnK@thomas>
Hi,
> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Thursday, April 14, 2022 4:03 PM
> To: Adham Masarwah <adham@nvidia.com>
> Cc: dev@dpdk.org; Matan Azrad <matan@nvidia.com>; Idan Hackmon
> <idanhac@nvidia.com>; Tamer Hleihel <tamerh@nvidia.com>; Tal
> Shnaiderman <talshn@nvidia.com>; Raslan Darawsheh
> <rasland@nvidia.com>
> Subject: Re: [PATCH] doc: update release notes for 22.07
>
> 14/04/2022 14:42, Adham Masarwah:
> > Added new features introduced to mlx5 related to Windows support.
> >
> > Signed-off-by: Adham Masarwah <adham@nvidia.com>
> > ---
> > +* **Updated Mellanox mlx5 driver.**
> > +
> > + * Added support for set promiscuous mode in Windows.
> > + * Added support for set and get MTU in Windows.
>
> Please, can it be squashed in relevant commits?
>
Squashed into relevant commits into master-net-mlx,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2022-04-17 6:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 12:42 Adham Masarwah
2022-04-14 13:02 ` Thomas Monjalon
2022-04-17 6:59 ` Raslan Darawsheh [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=BYAPR12MB30781FBA667FD8111A2A9FEFCFF09@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 \
/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).