From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, ferruh.yigit@intel.com, john.mcnamara@intel.com
Subject: Re: [PATCH v2] ethdev: introduce lock-free txq capability flag
Date: Mon, 10 Jul 2017 22:26:15 +0530 [thread overview]
Message-ID: <20170710165614.GA30545@jerin> (raw)
In-Reply-To: <187460180.BTNh70yjrI@xps>
-----Original Message-----
> Date: Sat, 08 Jul 2017 18:08:57 +0200
> From: Thomas Monjalon <thomas@monjalon.net>
> To: Jerin Jacob <jerin.jacob@caviumnetworks.com>
> Cc: dev@dpdk.org, ferruh.yigit@intel.com, john.mcnamara@intel.com
> Subject: Re: [dpdk-dev] [PATCH v2] ethdev: introduce lock-free txq
> capability flag
>
> Hi Jerin,
>
Hi Thomas. Thanks for the review.
> Thanks for the update.
> I think we can add this new flag in 17.08.
> I prefer waiting John's review, especially for doc wording,
Make sense. I will send the version.
> before applying it. I consider it does not hurt to add it post-rc1.
>
> See below for my first comment on the doc.
Fixed in next version.
next prev parent reply other threads:[~2017-07-10 16:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-21 12:22 [PATCH] ethdev: add lock-less txq capability flag Jerin Jacob
2017-04-24 12:34 ` Thomas Monjalon
2017-04-27 11:00 ` Jerin Jacob
2017-07-05 17:46 ` Thomas Monjalon
2017-07-06 6:00 ` Jerin Jacob
2017-07-06 6:21 ` [PATCH v2] ethdev: introduce lock-free " Jerin Jacob
2017-07-08 16:08 ` Thomas Monjalon
2017-07-10 16:56 ` Jerin Jacob [this message]
2017-07-10 16:59 ` [PATCH v3 ] " Jerin Jacob
2017-07-13 12:02 ` Hemant Agrawal
2017-07-18 13:43 ` Thomas Monjalon
2017-07-13 18:42 ` santosh
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=20170710165614.GA30545@jerin \
--to=jerin.jacob@caviumnetworks.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.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 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.