From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 0/2] small changes
Date: Wed, 8 Apr 2015 10:37:48 -0700 [thread overview]
Message-ID: <1428514670-7982-1-git-send-email-stephen@networkplumber.org> (raw)
These are trivial patches found by review
Stephen Hemminger (2):
enic: silence log message
tools: fix comment in bind script
lib/librte_pmd_enic/enic_main.c | 2 --
tools/dpdk_nic_bind.py | 2 +-
2 files changed, 1 insertion(+), 3 deletions(-)
--
2.1.4
next reply other threads:[~2015-04-08 17:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 17:37 Stephen Hemminger [this message]
2015-04-08 17:37 ` [dpdk-dev] [PATCH 1/2] enic: silence log message Stephen Hemminger
2015-05-19 10:08 ` Bruce Richardson
2015-05-20 16:30 ` Sujith Sankar (ssujith)
2015-05-20 17:47 ` Stephen Hemminger
2015-05-21 1:52 ` Sujith Sankar (ssujith)
2015-07-30 17:03 ` [dpdk-dev] [PATCH v2] enic: silence log message unless debug enabled Stephen Hemminger
2015-07-30 19:18 ` Thomas Monjalon
2015-04-08 17:37 ` [dpdk-dev] [PATCH 2/2] tools: fix comment in bind script Stephen Hemminger
2015-04-15 9:43 ` Bruce Richardson
2015-08-03 16:38 ` 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=1428514670-7982-1-git-send-email-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).