From: Thomas Monjalon <thomas@monjalon.net>
To: Harry van Haaren <harry.van.haaren@intel.com>
Cc: dev@dpdk.org, "Liang, Ma" <liang.j.ma@intel.com>,
peter.mccarthy@intel.com
Subject: Re: [dpdk-dev] [PATCH] event/opdl: rework loops to comply with dpdk style
Date: Wed, 24 Jan 2018 18:56:58 +0100 [thread overview]
Message-ID: <7526705.a3qLKkoPOQ@xps> (raw)
In-Reply-To: <20180122103001.GA9466@sivswdev01.ir.intel.com>
22/01/2018 11:30, Liang, Ma:
> On 22 Jan 10:04, Harry van Haaren wrote:
> > This commit reworks the loop counter variable declarations
> > to be in line with the DPDK source code.
> >
> > Fixes: 3c7f3dcfb099 ("event/opdl: add PMD main body and helper function")
> > Fixes: 8ca8e3b48eff ("event/opdl: add event queue config get/set")
> > Fixes: d548ef513cd7 ("event/opdl: add unit tests")
> >
> > Cc: liang.j.ma@intel.com
> > Cc: peter.mccarthy@intel.com
> >
> > Signed-off-by: Harry van Haaren <harry.van.haaren@intel.com>
> >
> > ---
> Many thanks Harry.
>
> Acked-by: Liang Ma <liang.j.ma@intel.com>
Applied, thanks
prev parent reply other threads:[~2018-01-24 17:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 10:04 Harry van Haaren
2018-01-22 10:30 ` Liang, Ma
2018-01-24 17:56 ` 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=7526705.a3qLKkoPOQ@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=harry.van.haaren@intel.com \
--cc=liang.j.ma@intel.com \
--cc=peter.mccarthy@intel.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).