DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Fady Bader <fady@mellanox.com>
Cc: dev@dpdk.org, tbashar@mellanox.com, talshn@mellanox.com,
	yohadt@mellanox.com, dmitry.kozliuk@gmail.com,
	harini.ramakrishnan@microsoft.com, ocardona@microsoft.com,
	pallavi.kadam@intel.com, Ranjit Menon <ranjit.menon@intel.com>
Subject: Re: [dpdk-dev] [PATCH v10 0/2] eal timer split and implementation for Windows
Date: Tue, 23 Jun 2020 18:19:43 +0200	[thread overview]
Message-ID: <3799342.ckjm8hCzun@thomas> (raw)
In-Reply-To: <d5e85101-b60a-220c-422a-187142bcf342@intel.com>

18/06/2020 21:32, Ranjit Menon:
> On 6/17/2020 11:55 PM, Fady Bader wrote:
> > This patchset splits OS dependent EAL timer functions and implements them for windows.
> >
> > v2:
> >      * fixing styles and correctness errors.
> > v3:
> >      * fixing correctness, get_tsc_freq was reimplemented.
> > v4:
> >      * rebasing to the new version of "Windows basic memory management" series.
> >      * fixing styles and correctness errors.
> > v5:
> >      * breaking the dependency on "Windows basic memory management" series.
> >      * fixing correctness errors and warnings.
> > v6:
> >      * fixing styles and correctness errors.
> > v7:
> >      * fixing make errors.
> > v8:
> >      * fixing error handling issue.
> >      * removed unneded headers.
> > v9:
> >      * rebasing to current master.
> >      * fixing correctness issue.
> > v10:
> >      * fixing correctness issue.
> >
> > Fady Bader (2):
> >    timer: move from common to Unix directory
> >    timer: support EAL functions on Windows
> >
> Acked-by: Ranjit Menon <ranjit.menon@intel.com>

Applied, thanks




  reply	other threads:[~2020-06-23 16:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-23 14:43 [dpdk-dev] [PATCH " Fady Bader
2020-04-23 14:43 ` [dpdk-dev] [PATCH 1/2] timer: move from common to Unix directory Fady Bader
2020-06-17  9:39   ` [dpdk-dev] [PATCH v9 0/2] eal timer split and implementation for Windows Fady Bader
2020-06-17  9:39     ` [dpdk-dev] [PATCH v9 1/2] timer: move from common to Unix directory Fady Bader
2020-06-17  9:39     ` [dpdk-dev] [PATCH v9 2/2] timer: support EAL functions on Windows Fady Bader
2020-06-17 22:15       ` Ranjit Menon
2020-06-18  7:56         ` Fady Bader
2020-06-18  6:55   ` [dpdk-dev] [PATCH v10 0/2] eal timer split and implementation for Windows Fady Bader
2020-06-18  6:55     ` [dpdk-dev] [PATCH v10 1/2] timer: move from common to Unix directory Fady Bader
2020-06-18  6:55     ` [dpdk-dev] [PATCH v10 2/2] timer: support EAL functions on Windows Fady Bader
2020-06-18 19:32     ` [dpdk-dev] [PATCH v10 0/2] eal timer split and implementation for Windows Ranjit Menon
2020-06-23 16:19       ` Thomas Monjalon [this message]
2020-04-23 14:43 ` [dpdk-dev] [PATCH 2/2] timer: support EAL functions on Windows Fady Bader
2020-04-23 15:18   ` Dmitry Kozlyuk
2020-04-24 21:32   ` Dmitry Kozlyuk

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=3799342.ckjm8hCzun@thomas \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=dmitry.kozliuk@gmail.com \
    --cc=fady@mellanox.com \
    --cc=harini.ramakrishnan@microsoft.com \
    --cc=ocardona@microsoft.com \
    --cc=pallavi.kadam@intel.com \
    --cc=ranjit.menon@intel.com \
    --cc=talshn@mellanox.com \
    --cc=tbashar@mellanox.com \
    --cc=yohadt@mellanox.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).