From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: Ori Kam <orika@nvidia.com>,
Aman Singh <aman.deep.singh@intel.com>,
Konstantin Ananyev <konstantin.ananyev@huawei.com>,
Nicolas Chautru <nicolas.chautru@intel.com>,
Gagandeep Singh <g.singh@nxp.com>,
Hemant Agrawal <hemant.agrawal@nxp.com>,
Kai Ji <kai.ji@intel.com>,
Pablo de Lara <pablo.de.lara.guarch@intel.com>,
Ajit Khaparde <ajit.khaparde@broadcom.com>,
Somnath Kotur <somnath.kotur@broadcom.com>,
Wenbo Cao <caowenbo@mucse.com>,
Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>,
Srikanth Yalavarthi <syalavarthi@marvell.com>
Subject: Re: [PATCH] fix after-code Doxygen comments
Date: Wed, 05 Nov 2025 22:34:36 +0100 [thread overview]
Message-ID: <2746681.0RtB02Ng89@thomas> (raw)
In-Reply-To: <20251102221400.4018641-1-thomas@monjalon.net>
02/11/2025 23:14, Thomas Monjalon:
> The comment syntax /*< is a mistake.
> The intent was to put a Doxygen comment after some code with /**<
> but an asterisk was missing.
>
> In cases of .c files with all other comments not using Doxygen syntax,
> it is converted into normal comment syntax.
>
> In cases the comment is completely useless, it is just removed.
>
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
I suppose there is not much to debate or review.
Applied
prev parent reply other threads:[~2025-11-05 21:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-02 22:14 [PATCH] fix after-code Doxygen comments Thomas Monjalon
2025-11-05 21:34 ` Thomas Monjalon [this message]
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=2746681.0RtB02Ng89@thomas \
--to=thomas@monjalon.net \
--cc=ajit.khaparde@broadcom.com \
--cc=aman.deep.singh@intel.com \
--cc=caowenbo@mucse.com \
--cc=dev@dpdk.org \
--cc=g.singh@nxp.com \
--cc=gmuthukrishn@marvell.com \
--cc=hemant.agrawal@nxp.com \
--cc=kai.ji@intel.com \
--cc=konstantin.ananyev@huawei.com \
--cc=nicolas.chautru@intel.com \
--cc=orika@nvidia.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=somnath.kotur@broadcom.com \
--cc=syalavarthi@marvell.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.