From: Hyong Youb Kim <hyonkim@cisco.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org, John Daley <johndale@cisco.com>,
Hyong Youb Kim <hyonkim@cisco.com>
Subject: [dpdk-dev] [PATCH 0/2] net/enic: two trivial fixes
Date: Mon, 14 Jan 2019 07:01:20 -0800 [thread overview]
Message-ID: <20190114150122.16999-1-hyonkim@cisco.com> (raw)
Hyong Youb Kim (2):
net/enic: remove useless include
net/enic: remove redundant log level check
drivers/net/enic/enic_clsf.c | 2 --
drivers/net/enic/enic_ethdev.c | 9 ++++-----
drivers/net/enic/enic_main.c | 1 -
3 files changed, 4 insertions(+), 8 deletions(-)
--
2.16.2
next reply other threads:[~2019-01-14 15:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-14 15:01 Hyong Youb Kim [this message]
2019-01-14 15:01 ` [dpdk-dev] [PATCH 1/2] net/enic: remove useless include Hyong Youb Kim
2019-01-14 15:01 ` [dpdk-dev] [PATCH 2/2] net/enic: remove redundant log level check Hyong Youb Kim
2019-01-14 16:41 ` [dpdk-dev] [PATCH 0/2] net/enic: two trivial fixes 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=20190114150122.16999-1-hyonkim@cisco.com \
--to=hyonkim@cisco.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=johndale@cisco.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).