DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: bruce.richardson@intel.com, pablo.de.lara.guarch@intel.com
Cc: dev@dpdk.org, mstolarchuk <mike.stolarchuk@bigswitch.com>
Subject: Re: [dpdk-dev] [PATCH 1/7] Use an accessor for rte_hash_key
Date: Tue, 17 Oct 2017 15:59:02 +0200	[thread overview]
Message-ID: <4317181.EN77ZZiejQ@xps> (raw)
In-Reply-To: <1503086972-32649-1-git-send-email-mike.stolarchuk@bigswitch.com>

18/08/2017 22:09, mstolarchuk:
> Improves consistency, allows identifcation of use-sites
> 
> Signed-off-by: mstolarchuk <mike.stolarchuk@bigswitch.com>

Any comment on this patch and others from the same author?

  reply	other threads:[~2017-10-17 13:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-18 20:09 mstolarchuk
2017-10-17 13:59 ` Thomas Monjalon [this message]
2017-10-19  8:10   ` De Lara Guarch, Pablo
2017-10-27 15:00     ` Mike Stolarchuk
2017-10-27 15:31       ` De Lara Guarch, Pablo
2019-03-01 17:15         ` Ferruh Yigit

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=4317181.EN77ZZiejQ@xps \
    --to=thomas@monjalon.net \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=mike.stolarchuk@bigswitch.com \
    --cc=pablo.de.lara.guarch@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).