From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [dpdk-dev] [PATCH 4/5] net/ipn3ke: cleanup blank line at eof
Date: Wed, 31 Jul 2019 07:57:41 -0700 [thread overview]
Message-ID: <20190731145742.10776-5-stephen@networkplumber.org> (raw)
In-Reply-To: <20190731145742.10776-1-stephen@networkplumber.org>
Leftover from editor? Remove blank lines at end of file.
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
drivers/net/ipn3ke/ipn3ke_flow.c | 1 -
drivers/net/ipn3ke/ipn3ke_tm.c | 1 -
2 files changed, 2 deletions(-)
diff --git a/drivers/net/ipn3ke/ipn3ke_flow.c b/drivers/net/ipn3ke/ipn3ke_flow.c
index f3aec979371d..9fc3c8bf763f 100644
--- a/drivers/net/ipn3ke/ipn3ke_flow.c
+++ b/drivers/net/ipn3ke/ipn3ke_flow.c
@@ -1372,4 +1372,3 @@ const struct rte_flow_ops ipn3ke_flow_ops = {
.destroy = ipn3ke_flow_destroy,
.flush = ipn3ke_flow_flush,
};
-
diff --git a/drivers/net/ipn3ke/ipn3ke_tm.c b/drivers/net/ipn3ke/ipn3ke_tm.c
index 10828fce006a..adf02c15705d 100644
--- a/drivers/net/ipn3ke/ipn3ke_tm.c
+++ b/drivers/net/ipn3ke/ipn3ke_tm.c
@@ -2060,4 +2060,3 @@ ipn3ke_tm_ops_get(struct rte_eth_dev *ethdev,
return 0;
}
-
--
2.20.1
next prev parent reply other threads:[~2019-07-31 14:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 14:57 [dpdk-dev] [PATCH 0/5] blank lines at EOF fixes Stephen Hemminger
2019-07-31 14:57 ` [dpdk-dev] [PATCH 1/5] examples: remove extra blank lines at eof Stephen Hemminger
2019-07-31 14:57 ` [dpdk-dev] [PATCH 2/5] test: remove " Stephen Hemminger
2019-07-31 14:57 ` [dpdk-dev] [PATCH 3/5] pmdinfogen: remove blank line " Stephen Hemminger
2019-07-31 14:57 ` Stephen Hemminger [this message]
2019-07-31 14:57 ` [dpdk-dev] [PATCH 5/5] net/mlx5: remove blank lines " Stephen Hemminger
2019-08-04 9:48 ` Slava Ovsiienko
2019-07-31 15:38 ` [dpdk-dev] [PATCH 0/5] blank lines at EOF fixes Bruce Richardson
2019-08-05 13:20 ` 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=20190731145742.10776-5-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).