All of lore.kernel.org
 help / color / mirror / Atom feed
From: Or Gerlitz <gerlitz.or@gmail.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, Wisam Jaddo <wisamm@mellanox.com>,
	 Andrew Rybchenko <arybchenko@solarflare.com>
Subject: Re: [dpdk-dev] [dpdk-announce] [HELP REQUIRED] call for reviews
Date: Sun, 28 Jun 2020 10:10:35 +0300	[thread overview]
Message-ID: <CAJ3xEMjtvo2uUY+kTLtRTLytHwAwLrvJPFG_KoC3qZ+ojuxLXw@mail.gmail.com> (raw)
In-Reply-To: <2013975.jpt7NDDz6o@thomas>

On Fri, Jun 26, 2020 at 7:43 PM Thomas Monjalon <thomas@monjalon.net> wrote:

> Our next milestone is approaching, 20.08-rc1 should be in 12 days :
>         http://core.dpdk.org/roadmap/#dates
> and the roadmap is very long:
>         http://core.dpdk.org/roadmap/#2008
>
> We all want to have our code reviewed and accepted.
> In order to have a small hope of reaching our goals,
> we need a large participation in reviews.
>
> PLEASE REVIEW some patches from the list below.
[..]

Hi Thomas,

Wanted to check re the flow perf application which AFAIK almost made it
for 20.05 but now is still waiting in patchworks [1]. I am using it and actually
there are few enhancements to be applied for serving more advanced use-cases
waiting for the initial acceptance to be submitted. I am politely
watching it in patchworks
without any real progress for couple of weeks.. so?

Thanks,

Or.

[1] https://patchwork.dpdk.org/cover/70851/

  reply	other threads:[~2020-06-28  7:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-26 16:43 [dpdk-dev] [dpdk-announce] [HELP REQUIRED] call for reviews Thomas Monjalon
2020-06-28  7:10 ` Or Gerlitz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-04-01  1:29 Thomas Monjalon
2020-04-01  9:11 ` Kevin Traynor

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=CAJ3xEMjtvo2uUY+kTLtRTLytHwAwLrvJPFG_KoC3qZ+ojuxLXw@mail.gmail.com \
    --to=gerlitz.or@gmail.com \
    --cc=arybchenko@solarflare.com \
    --cc=dev@dpdk.org \
    --cc=thomas@monjalon.net \
    --cc=wisamm@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.