* [dpdk-dev] [PATCH] mem: fix incorrect doxygen doc regarding memzones
@ 2015-11-18 15:58 Sergio Gonzalez Monroy
2015-11-18 17:43 ` Mcnamara, John
0 siblings, 1 reply; 3+ messages in thread
From: Sergio Gonzalez Monroy @ 2015-11-18 15:58 UTC (permalink / raw)
To: dev
We can free memzones now, so remove incorrect doxygen documentation
stating otherwise.
Fixes: ff909fe21f0a ("mem: introduce memzone freeing")
Signed-off-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
---
lib/librte_eal/common/include/rte_memzone.h | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/lib/librte_eal/common/include/rte_memzone.h b/lib/librte_eal/common/include/rte_memzone.h
index 53f4232..f69b5a8 100644
--- a/lib/librte_eal/common/include/rte_memzone.h
+++ b/lib/librte_eal/common/include/rte_memzone.h
@@ -100,7 +100,7 @@ struct rte_memzone {
*
* This function reserves some memory and returns a pointer to a
* correctly filled memzone descriptor. If the allocation cannot be
- * done, return NULL. Note: A reserved zone cannot be freed.
+ * done, return NULL.
*
* @param name
* The name of the memzone. If it already exists, the function will
@@ -151,7 +151,6 @@ const struct rte_memzone *rte_memzone_reserve(const char *name,
* boundary, and returns a pointer to a correctly filled memzone
* descriptor. If the allocation cannot be done or if the alignment
* is not a power of 2, returns NULL.
- * Note: A reserved zone cannot be freed.
*
* @param name
* The name of the memzone. If it already exists, the function will
@@ -207,7 +206,6 @@ const struct rte_memzone *rte_memzone_reserve_aligned(const char *name,
* Memory buffer is reserved in a way, that it wouldn't cross specified
* boundary. That implies that requested length should be less or equal
* then boundary.
- * Note: A reserved zone cannot be freed.
*
* @param name
* The name of the memzone. If it already exists, the function will
--
2.4.3
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [dpdk-dev] [PATCH] mem: fix incorrect doxygen doc regarding memzones
2015-11-18 15:58 [dpdk-dev] [PATCH] mem: fix incorrect doxygen doc regarding memzones Sergio Gonzalez Monroy
@ 2015-11-18 17:43 ` Mcnamara, John
2015-12-06 21:19 ` Thomas Monjalon
0 siblings, 1 reply; 3+ messages in thread
From: Mcnamara, John @ 2015-11-18 17:43 UTC (permalink / raw)
To: Gonzalez Monroy, Sergio, dev
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Sergio Gonzalez
> Monroy
> Sent: Wednesday, November 18, 2015 3:58 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH] mem: fix incorrect doxygen doc regarding
> memzones
>
> We can free memzones now, so remove incorrect doxygen documentation
> stating otherwise.
>
> Fixes: ff909fe21f0a ("mem: introduce memzone freeing")
>
> Signed-off-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
Acked-by: John McNamara <john.mcnamara@intel.com>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [dpdk-dev] [PATCH] mem: fix incorrect doxygen doc regarding memzones
2015-11-18 17:43 ` Mcnamara, John
@ 2015-12-06 21:19 ` Thomas Monjalon
0 siblings, 0 replies; 3+ messages in thread
From: Thomas Monjalon @ 2015-12-06 21:19 UTC (permalink / raw)
To: Gonzalez Monroy, Sergio; +Cc: dev
> > We can free memzones now, so remove incorrect doxygen documentation
> > stating otherwise.
> >
> > Fixes: ff909fe21f0a ("mem: introduce memzone freeing")
> >
> > Signed-off-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
>
> Acked-by: John McNamara <john.mcnamara@intel.com>
Applied, thanks
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2015-12-06 21:20 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-11-18 15:58 [dpdk-dev] [PATCH] mem: fix incorrect doxygen doc regarding memzones Sergio Gonzalez Monroy
2015-11-18 17:43 ` Mcnamara, John
2015-12-06 21:19 ` Thomas Monjalon
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).