From: christian.ehrhardt@canonical.com
To: Jerin Jacob <jerinj@marvell.com>
Cc: dpdk stable <stable@dpdk.org>
Subject: patch 'eal: fix doxygen comments for UUID' has been queued to stable release 19.11.14
Date: Wed, 16 Nov 2022 11:40:00 +0100 [thread overview]
Message-ID: <20221116104012.2975036-5-christian.ehrhardt@canonical.com> (raw)
In-Reply-To: <20221116104012.2975036-1-christian.ehrhardt@canonical.com>
Hi,
FYI, your patch has been queued to stable release 19.11.14
Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet.
It will be pushed if I get no objections before 11/23/22. So please
shout if anyone has objections.
Also note that after the patch there's a diff of the upstream commit vs the
patch applied to the branch. This will indicate if there was any rebasing
needed to apply to the stable branch. If there were code changes for rebasing
(ie: not only metadata diffs), please double check that the rebase was
correctly done.
Queued patches are on a temporary branch at:
https://github.com/cpaelzer/dpdk-stable-queue
This queued commit can be viewed at:
https://github.com/cpaelzer/dpdk-stable-queue/commit/e922afb57478f9dcf993197afcea4b2ea9555ccb
Thanks.
Christian Ehrhardt <christian.ehrhardt@canonical.com>
---
From e922afb57478f9dcf993197afcea4b2ea9555ccb Mon Sep 17 00:00:00 2001
From: Jerin Jacob <jerinj@marvell.com>
Date: Wed, 9 Nov 2022 20:24:10 +0530
Subject: [PATCH] eal: fix doxygen comments for UUID
[ upstream commit 61c7dfe75a9ab345bbd8bdc30c2da0ee661660a8 ]
Fix following syntax error reported by doxygen 1.9.5 version.
lib/eal/include/rte_uuid.h:89: error: RTE_UUID_STRLEN
has @param documentation sections but no arguments
(warning treated as error, aborting now)
Fixes: 6bc67c497a51 ("eal: add uuid API")
Signed-off-by: Jerin Jacob <jerinj@marvell.com>
---
lib/librte_eal/common/include/rte_uuid.h | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/lib/librte_eal/common/include/rte_uuid.h b/lib/librte_eal/common/include/rte_uuid.h
index 8b42e070af..cfefd4308a 100644
--- a/lib/librte_eal/common/include/rte_uuid.h
+++ b/lib/librte_eal/common/include/rte_uuid.h
@@ -37,6 +37,9 @@ typedef unsigned char rte_uuid_t[16];
((e) >> 8) & 0xff, (e) & 0xff \
}
+/** UUID string length */
+#define RTE_UUID_STRLEN (36 + 1)
+
/**
* Test if UUID is all zeros.
*
@@ -95,7 +98,6 @@ int rte_uuid_parse(const char *in, rte_uuid_t uu);
* @param len
* Sizeof the available string buffer
*/
-#define RTE_UUID_STRLEN (36 + 1)
void rte_uuid_unparse(const rte_uuid_t uu, char *out, size_t len);
#ifdef __cplusplus
--
2.38.1
---
Diff of the applied patch vs upstream commit (please double-check if non-empty:
---
--- - 2022-11-16 11:36:50.617945255 +0100
+++ 0005-eal-fix-doxygen-comments-for-UUID.patch 2022-11-16 11:36:50.404775402 +0100
@@ -1 +1 @@
-From 61c7dfe75a9ab345bbd8bdc30c2da0ee661660a8 Mon Sep 17 00:00:00 2001
+From e922afb57478f9dcf993197afcea4b2ea9555ccb Mon Sep 17 00:00:00 2001
@@ -5,0 +6,2 @@
+[ upstream commit 61c7dfe75a9ab345bbd8bdc30c2da0ee661660a8 ]
+
@@ -13 +14,0 @@
-Cc: stable@dpdk.org
@@ -17 +18 @@
- lib/eal/include/rte_uuid.h | 4 +++-
+ lib/librte_eal/common/include/rte_uuid.h | 4 +++-
@@ -20 +21 @@
-diff --git a/lib/eal/include/rte_uuid.h b/lib/eal/include/rte_uuid.h
+diff --git a/lib/librte_eal/common/include/rte_uuid.h b/lib/librte_eal/common/include/rte_uuid.h
@@ -22,2 +23,2 @@
---- a/lib/eal/include/rte_uuid.h
-+++ b/lib/eal/include/rte_uuid.h
+--- a/lib/librte_eal/common/include/rte_uuid.h
++++ b/lib/librte_eal/common/include/rte_uuid.h
next prev parent reply other threads:[~2022-11-16 10:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 10:39 patch 'net/bonding: set initial value of descriptor count alignment' " christian.ehrhardt
2022-11-16 10:39 ` patch 'net/bonding: fix dropping valid MAC packets' " christian.ehrhardt
2022-11-16 10:39 ` patch 'app/testpmd: make quit flag volatile' " christian.ehrhardt
2022-11-16 10:39 ` patch 'net/bonding: fix mbuf fast free handling' " christian.ehrhardt
2022-11-16 10:40 ` christian.ehrhardt [this message]
2022-11-16 10:40 ` patch 'power: fix some doxygen comments' " christian.ehrhardt
2022-11-16 10:40 ` patch 'test/hash: remove dead code in extendable bucket test' " christian.ehrhardt
2022-11-16 10:40 ` patch 'net/mlx5: fix hairpin split with set VLAN VID action' " christian.ehrhardt
2022-11-16 10:40 ` patch 'net/ice/base: fix duplicate flow rules' " christian.ehrhardt
2022-11-16 10:40 ` patch 'net/ice: fix scalar Rx path segment' " christian.ehrhardt
2022-11-16 10:40 ` patch 'net/ice: fix scalar Tx " christian.ehrhardt
2022-11-16 10:40 ` patch 'examples/fips_validation: fix typo in error log' " christian.ehrhardt
2022-11-16 10:40 ` patch 'test/crypto: fix bitwise operator in a SNOW3G case' " christian.ehrhardt
2022-11-16 10:40 ` patch 'doc: fix typo depreciated instead of deprecated' " christian.ehrhardt
2022-11-16 10:40 ` patch 'drivers: fix typos found by Lintian' " christian.ehrhardt
2022-11-16 10:40 ` patch 'doc: fix net drivers ordering' " christian.ehrhardt
2022-11-16 10:40 ` patch 'ring: remove leftover comment about watermark' " christian.ehrhardt
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=20221116104012.2975036-5-christian.ehrhardt@canonical.com \
--to=christian.ehrhardt@canonical.com \
--cc=jerinj@marvell.com \
--cc=stable@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).