From: Harry van Haaren <harry.van.haaren@intel.com>
To: remy.horton@intel.com
Cc: dev@dpdk.org
Subject: [dpdk-dev] [PATCH v4 3/3] keepalive: fix whitespace, removes double newlines
Date: Tue, 8 Mar 2016 10:50:40 +0000 [thread overview]
Message-ID: <1457434240-13707-4-git-send-email-harry.van.haaren@intel.com> (raw)
In-Reply-To: <1457434240-13707-1-git-send-email-harry.van.haaren@intel.com>
This patch removes double newlines between functions
in keepalive.[hc] aligning it with the rest of DPDK.
Fixes: 75583b0d1efd ("eal: add keep alive monitoring")
Signed-off-by: Harry van Haaren <harry.van.haaren@intel.com>
---
lib/librte_eal/common/include/rte_keepalive.h | 7 -------
lib/librte_eal/common/rte_keepalive.c | 5 -----
2 files changed, 12 deletions(-)
diff --git a/lib/librte_eal/common/include/rte_keepalive.h b/lib/librte_eal/common/include/rte_keepalive.h
index f4cec04..10dac2e 100644
--- a/lib/librte_eal/common/include/rte_keepalive.h
+++ b/lib/librte_eal/common/include/rte_keepalive.h
@@ -48,7 +48,6 @@
#define RTE_KEEPALIVE_MAXCORES RTE_MAX_LCORE
#endif
-
/**
* Keepalive failure callback.
*
@@ -59,14 +58,12 @@ typedef void (*rte_keepalive_failure_callback_t)(
void *data,
const int id_core);
-
/**
* Keepalive state structure.
* @internal
*/
struct rte_keepalive;
-
/**
* Initialise keepalive sub-system.
* @param callback
@@ -80,7 +77,6 @@ struct rte_keepalive *rte_keepalive_create(
rte_keepalive_failure_callback_t callback,
void *data);
-
/**
* Checks & handles keepalive state of monitored cores.
* @param *ptr_timer Triggering timer (unused)
@@ -88,7 +84,6 @@ struct rte_keepalive *rte_keepalive_create(
*/
void rte_keepalive_dispatch_pings(void *ptr_timer, void *ptr_data);
-
/**
* Registers a core for keepalive checks.
* @param *keepcfg
@@ -99,7 +94,6 @@ void rte_keepalive_dispatch_pings(void *ptr_timer, void *ptr_data);
void rte_keepalive_register_core(struct rte_keepalive *keepcfg,
const int id_core);
-
/**
* Per-core keepalive check.
* @param *keepcfg
@@ -111,5 +105,4 @@ void rte_keepalive_register_core(struct rte_keepalive *keepcfg,
void
rte_keepalive_mark_alive(struct rte_keepalive *keepcfg);
-
#endif /* _KEEPALIVE_H_ */
diff --git a/lib/librte_eal/common/rte_keepalive.c b/lib/librte_eal/common/rte_keepalive.c
index 56df0b1..23363ec 100644
--- a/lib/librte_eal/common/rte_keepalive.c
+++ b/lib/librte_eal/common/rte_keepalive.c
@@ -70,7 +70,6 @@ struct rte_keepalive {
uint64_t tsc_mhz;
};
-
static void
print_trace(const char *msg, struct rte_keepalive *keepcfg, int idx_core)
{
@@ -81,7 +80,6 @@ print_trace(const char *msg, struct rte_keepalive *keepcfg, int idx_core)
);
}
-
void
rte_keepalive_dispatch_pings(__rte_unused void *ptr_timer,
void *ptr_data)
@@ -117,7 +115,6 @@ rte_keepalive_dispatch_pings(__rte_unused void *ptr_timer,
}
}
-
struct rte_keepalive *
rte_keepalive_create(rte_keepalive_failure_callback_t callback,
void *data)
@@ -136,7 +133,6 @@ rte_keepalive_create(rte_keepalive_failure_callback_t callback,
return keepcfg;
}
-
void
rte_keepalive_register_core(struct rte_keepalive *keepcfg, const int id_core)
{
@@ -146,7 +142,6 @@ rte_keepalive_register_core(struct rte_keepalive *keepcfg, const int id_core)
}
}
-
void
rte_keepalive_mark_alive(struct rte_keepalive *keepcfg)
{
--
2.5.0
next prev parent reply other threads:[~2016-03-08 10:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-20 15:53 [dpdk-dev] [PATCH 0/3] Keep-alive stats and doc fixes Harry van Haaren
2016-01-20 15:53 ` [dpdk-dev] [PATCH 1/3] doc: fix keepalive sample app guide Harry van Haaren
2016-01-20 15:53 ` [dpdk-dev] [PATCH 2/3] eal: add keepalive core register timestamp Harry van Haaren
2016-01-20 15:53 ` [dpdk-dev] [PATCH 3/3] keepalive: add rte_keepalive_xstats() and example Harry van Haaren
2016-01-21 9:57 ` Remy Horton
2016-01-21 11:05 ` [dpdk-dev] [PATCH v2 0/3] Keep-alive stats and doc fixes Harry van Haaren
2016-01-21 11:05 ` [dpdk-dev] [PATCH v2 1/3] doc: fix keepalive sample app guide Harry van Haaren
2016-02-19 17:28 ` Mcnamara, John
2016-01-21 11:05 ` [dpdk-dev] [PATCH v2 2/3] eal: add keepalive core register timestamp Harry van Haaren
2016-01-21 11:05 ` [dpdk-dev] [PATCH v2 3/3] keepalive: add rte_keepalive_xstats_get() and example Harry van Haaren
2016-01-21 12:12 ` [dpdk-dev] [PATCH v2 0/3] Keep-alive stats and doc fixes Remy Horton
2016-02-22 11:25 ` [dpdk-dev] [PATCH v3 0/3] Keepalive stats function " Harry van Haaren
2016-02-22 11:26 ` [dpdk-dev] [PATCH v3 1/3] doc: fix keepalive sample app guide Harry van Haaren
2016-02-22 16:54 ` Mcnamara, John
2016-02-22 11:26 ` [dpdk-dev] [PATCH v3 2/3] eal: add keepalive core register timestamp Harry van Haaren
2016-02-22 11:26 ` [dpdk-dev] [PATCH v3 3/3] keepalive: add rte_keepalive_xstats_get() Harry van Haaren
2016-02-29 9:19 ` Thomas Monjalon
2016-02-22 13:12 ` [dpdk-dev] [PATCH v3 0/3] Keepalive stats function and doc fixes Remy Horton
2016-03-08 10:50 ` [dpdk-dev] [PATCH v4 0/3] Keepalive register timestamp and doc update Harry van Haaren
2016-03-08 10:50 ` [dpdk-dev] [PATCH v4 1/3] doc: fix keepalive sample app guide Harry van Haaren
2016-03-08 10:50 ` [dpdk-dev] [PATCH v4 2/3] eal: add keepalive core register timestamp Harry van Haaren
2016-03-08 10:50 ` Harry van Haaren [this message]
2016-03-08 10:58 ` [dpdk-dev] [PATCH v4 0/3] Keepalive register timestamp and doc update 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=1457434240-13707-4-git-send-email-harry.van.haaren@intel.com \
--to=harry.van.haaren@intel.com \
--cc=dev@dpdk.org \
--cc=remy.horton@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 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).