From: Rami Rosen <ramirose@gmail.com>
To: dev@dpdk.org
Cc: jijiang.liu@intel.com, xiaoyun.li@intel.com,
Rami Rosen <ramirose@gmail.com>,
stable@dpdk.org
Subject: [PATCH] examples/tep_term: remove MAX_PRINT_BUFF
Date: Sun, 13 Jan 2019 17:02:12 +0200 [thread overview]
Message-ID: <1547391732-6215-1-git-send-email-ramirose@gmail.com> (raw)
The definition of MAX_PRINT_BUFF in examples/tep_termination/main.c
is not necessary as it is not used. This cleanup patch removes it.
Fixes: a50245ede72a ("examples/tep_term: initialize VXLAN sample")
Cc: stable@dpdk.org
Signed-off-by: Rami Rosen <ramirose@gmail.com>
---
examples/tep_termination/main.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/examples/tep_termination/main.c b/examples/tep_termination/main.c
index 7795d08..d6379e3 100644
--- a/examples/tep_termination/main.c
+++ b/examples/tep_termination/main.c
@@ -71,9 +71,6 @@
#define INVALID_PORT_ID 0xFFFF
-/* Size of buffers used for snprintfs. */
-#define MAX_PRINT_BUFF 6072
-
/* Maximum character device basename size. */
#define MAX_BASENAME_SZ 20
--
1.8.3.1
next reply other threads:[~2019-01-13 15:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-13 15:02 Rami Rosen [this message]
2019-01-15 0:35 ` [PATCH] examples/tep_term: remove MAX_PRINT_BUFF 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=1547391732-6215-1-git-send-email-ramirose@gmail.com \
--to=ramirose@gmail.com \
--cc=dev@dpdk.org \
--cc=jijiang.liu@intel.com \
--cc=stable@dpdk.org \
--cc=xiaoyun.li@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.