From: David Marchand <david.marchand@redhat.com>
To: Ali Alnubani <alialnu@nvidia.com>
Cc: "luca.boccassi@gmail.com" <luca.boccassi@gmail.com>,
"stable@dpdk.org" <stable@dpdk.org>,
"dev@dpdk.org" <dev@dpdk.org>,
Abhishek Marathe <Abhishek.Marathe@microsoft.com>,
"benjamin.walker@intel.com" <benjamin.walker@intel.com>,
David Christensen <drc@linux.vnet.ibm.com>,
Hemant Agrawal <hemant.agrawal@nxp.com>,
Ian Stokes <ian.stokes@intel.com>,
Jerin Jacob <jerinj@marvell.com>,
John McNamara <john.mcnamara@intel.com>,
Ju-Hyoung Lee <juhlee@microsoft.com>,
Kevin Traynor <ktraynor@redhat.com>,
Luca Boccassi <bluca@debian.org>, Pei Zhang <pezhang@redhat.com>,
"qian.q.xu@intel.com" <qian.q.xu@intel.com>,
Raslan Darawsheh <rasland@nvidia.com>,
"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>,
Yanghang Liu <yanghliu@redhat.com>,
"yuan.peng@intel.com" <yuan.peng@intel.com>,
"zhaoyan.chen@intel.com" <zhaoyan.chen@intel.com>
Subject: Re: 20.11.8 patches review and test
Date: Wed, 19 Apr 2023 15:11:41 +0200 [thread overview]
Message-ID: <CAJFAV8xxMy7EBz8FtPesK1BpvOqO0t6NDmDngV4sfRsOBcJLeg@mail.gmail.com> (raw)
In-Reply-To: <DM4PR12MB516746868954C470EFF9E305DA629@DM4PR12MB5167.namprd12.prod.outlook.com>
Hello Ali,
On Wed, Apr 19, 2023 at 11:22 AM Ali Alnubani <alialnu@nvidia.com> wrote:
> I see this documentation build failure on Fedora 37:
>
> $ ninja-build -C build doc
> [..]
> [2/4] Generating doc/api/doxygen with a custom command
> FAILED: doc/api/html
> /root/dpdk/doc/api/generate_doxygen.sh doc/api/doxy-api.conf doc/api/html /root/dpdk/doc/api/doxy-html-custom.sh
> /root/dpdk/lib/librte_cryptodev/rte_cryptodev_pmd.h:489: error: found documented return type for rte_cryptodev_pmd_callback_process that does not return anything (warning treated as error, aborting now)
> [..]
> ninja: build stopped: subcommand failed.
This looks a lot like: 16de054160e3 ("lib: remove empty return types
from doxygen comments")
I don't think this function prototype is really different in the 20.11
stable branch (putting the __rte_internal tag aside).
Can you trigger this issue on the main branch?
--
David Marchand
next prev parent reply other threads:[~2023-04-19 13:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 18:20 luca.boccassi
2023-04-06 7:19 ` Xu, HailinX
2023-04-11 5:17 ` Xu, HailinX
2023-04-14 10:06 ` Luca Boccassi
2023-04-17 10:34 ` Xu, HailinX
2023-04-12 15:15 ` Ali Alnubani
2023-04-14 8:28 ` YangHang Liu
2023-04-19 9:22 ` Ali Alnubani
2023-04-19 13:02 ` Luca Boccassi
2023-04-19 13:10 ` Ali Alnubani
2023-04-19 13:11 ` David Marchand [this message]
2023-04-19 13:14 ` Ali Alnubani
2023-04-19 13:24 ` David Marchand
2023-04-19 14:14 ` Luca Boccassi
2023-04-19 14:23 ` Ali Alnubani
2023-04-19 14:26 ` Kevin Traynor
2023-04-19 14:30 ` Luca Boccassi
2023-04-19 14:35 ` Ali Alnubani
2023-04-19 14:35 ` David Marchand
2023-04-19 14:38 ` Luca Boccassi
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=CAJFAV8xxMy7EBz8FtPesK1BpvOqO0t6NDmDngV4sfRsOBcJLeg@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=Abhishek.Marathe@microsoft.com \
--cc=alialnu@nvidia.com \
--cc=benjamin.walker@intel.com \
--cc=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=drc@linux.vnet.ibm.com \
--cc=hemant.agrawal@nxp.com \
--cc=ian.stokes@intel.com \
--cc=jerinj@marvell.com \
--cc=john.mcnamara@intel.com \
--cc=juhlee@microsoft.com \
--cc=ktraynor@redhat.com \
--cc=luca.boccassi@gmail.com \
--cc=pezhang@redhat.com \
--cc=qian.q.xu@intel.com \
--cc=rasland@nvidia.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=yanghliu@redhat.com \
--cc=yuan.peng@intel.com \
--cc=zhaoyan.chen@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).