DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [dpdk-dev] [PATCH v2 0/2] eal: hexdump cleanups
Date: Tue,  2 Apr 2019 08:23:48 -0700	[thread overview]
Message-ID: <20190402152350.17572-1-stephen@networkplumber.org> (raw)
Message-ID: <20190402152348.rAB3jwzqttQnrzdaIIFCpAoNQlR2goYRclwo1ZNRotc@z> (raw)
In-Reply-To: <20180816153106.7608-1-stephen@networkplumber.org>

Minor bugfix and source cleanup

Stephen Hemminger (2):
  hexdump: whitespace cleanup
  hexdump: align output of string

 lib/librte_eal/common/eal_common_hexdump.c | 114 +++++++++------------
 1 file changed, 50 insertions(+), 64 deletions(-)

-- 
2.17.1


  parent reply	other threads:[~2019-04-02 15:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-16 15:31 [dpdk-dev] [PATCH 0/2] eal: hexcump trivial changes Stephen Hemminger
2018-08-16 15:31 ` [dpdk-dev] [PATCH 1/2] hexdump: whitespace cleanup Stephen Hemminger
2018-08-16 16:34   ` Wiles, Keith
2018-08-16 16:59     ` Stephen Hemminger
2018-08-16 16:35   ` Wiles, Keith
2018-08-16 15:31 ` [dpdk-dev] [PATCH 2/2] hexdump: align output of string Stephen Hemminger
2018-08-16 15:50   ` Stephen Hemminger
2018-10-24 23:40 ` [dpdk-dev] [PATCH 0/2] eal: hexcump trivial changes Thomas Monjalon
2019-04-02 15:23 ` Stephen Hemminger [this message]
2019-04-02 15:23   ` [dpdk-dev] [PATCH v2 0/2] eal: hexdump cleanups Stephen Hemminger
2019-04-02 15:23   ` [dpdk-dev] [PATCH v2 1/2] hexdump: whitespace cleanup Stephen Hemminger
2019-04-02 15:23     ` Stephen Hemminger
2019-04-02 15:23   ` [dpdk-dev] [PATCH v2 2/2] hexdump: align output of string Stephen Hemminger
2019-04-02 15:23     ` Stephen Hemminger
2019-04-03 16:36   ` [dpdk-dev] [PATCH v2 0/2] eal: hexdump cleanups Thomas Monjalon
2019-04-03 16:36     ` 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=20190402152350.17572-1-stephen@networkplumber.org \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    /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).