DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
To: "Singh, Jasvinder" <jasvinder.singh@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v3] ip_pipeline: add flow id parameter to flow classification
Date: Mon, 12 Oct 2015 15:46:31 +0000	[thread overview]
Message-ID: <3EB4FA525960D640B5BDFFD6A3D89126478EE2FB@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1444664499-32742-1-git-send-email-jasvinder.singh@intel.com>



> -----Original Message-----
> From: Singh, Jasvinder
> Sent: Monday, October 12, 2015 4:42 PM
> To: dev@dpdk.org
> Cc: Dumitrescu, Cristian
> Subject: [PATCH v3] ip_pipeline: add flow id parameter to flow classification
> 
> *v3
> fixed bug: changed LRU hash table operation to
> extendible bucket hash table operation
> 
> Signed-off-by: Jasvinder Singh <jasvinder.singh@intel.com>
> ---


Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>

Jasvinder, next time we send new patch version with just a small modification (like this one), you can also include my Ack line from the previous version (just under the signoff line), as Thomas kindly suggested.

  reply	other threads:[~2015-10-12 15:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1444043619-1343-1-git-send-email-jasvinder.singh@intel.com>
2015-10-05 13:10 ` [dpdk-dev] [PATCH v2] " Dumitrescu, Cristian
2015-10-12 15:41 ` [dpdk-dev] [PATCH v3] " Jasvinder Singh
2015-10-12 15:46   ` Dumitrescu, Cristian [this message]
2015-10-12 15:51     ` Singh, Jasvinder
2015-11-30 14:08 ` [dpdk-dev] [PATCH v4] " Jasvinder Singh
2015-12-07  0:50   ` Thomas Monjalon

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=3EB4FA525960D640B5BDFFD6A3D89126478EE2FB@IRSMSX108.ger.corp.intel.com \
    --to=cristian.dumitrescu@intel.com \
    --cc=dev@dpdk.org \
    --cc=jasvinder.singh@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).