From: Michal Krawczyk <mk@semihalf.com>
To: dev@dpdk.org, Robert Sanford <rsanford@akamai.com>,
Erik Gabriel Carrillo <erik.g.carrillo@intel.com>
Cc: Stanislaw Kardach <kda@semihalf.com>, Michal Krawczyk <mk@semihalf.com>
Subject: [dpdk-dev] [PATCH 1/2] timer: clarify subsystem_init return value
Date: Fri, 26 Mar 2021 11:47:58 +0100 [thread overview]
Message-ID: <20210326104759.280175-2-mk@semihalf.com> (raw)
In-Reply-To: <20210326104759.280175-1-mk@semihalf.com>
From: Stanislaw Kardach <kda@semihalf.com>
rte_timer_subsystem_init() may return -EALREADY if it has been already
initialized. Therefore put explicitly into doxygen that this is not a
failure for the application.
Signed-off-by: Stanislaw Kardach <kda@semihalf.com>
Reviewed-by: Michal Krawczyk <mk@semihalf.com>
---
lib/librte_timer/rte_timer.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/lib/librte_timer/rte_timer.h b/lib/librte_timer/rte_timer.h
index 22a27aa08d..0f820555c0 100644
--- a/lib/librte_timer/rte_timer.h
+++ b/lib/librte_timer/rte_timer.h
@@ -171,6 +171,7 @@ int rte_timer_data_dealloc(uint32_t id);
* - 0: Success
* - -ENOMEM: Unable to allocate memory needed to initialize timer
* subsystem
+ * - -EALREADY: timer subsystem was already initialized. Not an error.
*/
int rte_timer_subsystem_init(void);
--
2.25.1
next prev parent reply other threads:[~2021-03-26 10:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-26 10:47 [dpdk-dev] [PATCH 0/2] Fix unit tests execution for ENA PMD Michal Krawczyk
2021-03-26 10:47 ` Michal Krawczyk [this message]
2021-03-29 20:50 ` [dpdk-dev] [PATCH 1/2] timer: clarify subsystem_init return value Carrillo, Erik G
2021-03-26 10:47 ` [dpdk-dev] [PATCH 2/2] test: proceed if timer subsystem was initialized Michal Krawczyk
2021-04-06 15:24 ` Thomas Monjalon
2021-04-06 15:31 ` Stanisław Kardach
2021-04-06 15:40 ` Thomas Monjalon
2021-04-08 21:15 ` [dpdk-dev] [PATCH 0/2] Fix unit tests execution for ENA PMD 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=20210326104759.280175-2-mk@semihalf.com \
--to=mk@semihalf.com \
--cc=dev@dpdk.org \
--cc=erik.g.carrillo@intel.com \
--cc=kda@semihalf.com \
--cc=rsanford@akamai.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).