From: Thomas Monjalon <thomas@monjalon.net>
To: Ophir Munk <ophirmu@nvidia.com>
Cc: dev@dpdk.org, Raslan Darawsheh <rasland@nvidia.com>,
Matan Azrad <matan@nvidia.com>,
Tal Shnaiderman <talshn@nvidia.com>
Subject: Re: [dpdk-dev] [PATCH v1 0/2] Windows sampling actions
Date: Wed, 06 Jan 2021 23:03:06 +0100 [thread overview]
Message-ID: <4328901.XAl4aNZvIP@thomas> (raw)
In-Reply-To: <20210103121550.30824-1-ophirmu@nvidia.com>
03/01/2021 13:15, Ophir Munk:
> v1: First release
>
> Ophir Munk (2):
> net/mlx5/linux: wrap sampling actions with OS calls
> net/mlx5/windows: implement sampling actions wrappers
I don't see a need to split Linux and Windows changes.
Squashed in one commit in next-net-mlx, thanks.
prev parent reply other threads:[~2021-01-06 22:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-03 12:15 Ophir Munk
2021-01-03 12:15 ` [dpdk-dev] [PATCH v1 1/2] net/mlx5/linux: wrap sampling actions with OS calls Ophir Munk
2021-01-03 12:15 ` [dpdk-dev] [PATCH v1 2/2] net/mlx5/windows: implement sampling actions wrappers Ophir Munk
2021-01-06 22:03 ` Thomas Monjalon [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=4328901.XAl4aNZvIP@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=ophirmu@nvidia.com \
--cc=rasland@nvidia.com \
--cc=talshn@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).