From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Stephen Hemminger" <stephen@networkplumber.org>, <dev@dpdk.org>
Cc: "Cristian Dumitrescu" <cristian.dumitrescu@intel.com>,
"Tyler Retzlaff" <roretzla@linux.microsoft.com>
Subject: RE: [PATCH] bitmap: change return value of rte_bitmap_free
Date: Wed, 29 Oct 2025 01:15:23 +0100 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35F65512@smartserver.smartshare.dk> (raw)
In-Reply-To: <20251028204432.880074-1-stephen@networkplumber.org>
> From: Stephen Hemminger [mailto:stephen@networkplumber.org]
> Sent: Tuesday, 28 October 2025 21.45
>
> No existing code is checking the return value of rte_bitmap_free
> and other functions like rte_free do not return an int.
> Change it to just a stub void function.
>
> This was motivated by Coverity warnings about unchecked return
> value.
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
Thank you for cleaning up this.
With or without suggestion inline below,
Reviewed-by: Morten Brørup <mb@smartsharesystems.com>
> /**
> - * Bitmap free
> + * Bitmap free does nothing in current version.
Consider keeping the original headline and adding a note that it does nothing in current version instead.
> *
> * @param bmp
> * Handle to bitmap instance
> - * @return
> - * 0 upon success, error code otherwise
> */
> -static inline int
> -rte_bitmap_free(struct rte_bitmap *bmp)
> +static inline void
> +rte_bitmap_free(struct rte_bitmap *bmp __rte_unused)
> {
> - /* Check input arguments */
> - if (bmp == NULL) {
> - return -1;
> - }
> -
> - return 0;
> }
next prev parent reply other threads:[~2025-10-29 0:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-28 20:44 Stephen Hemminger
2025-10-29 0:15 ` Morten Brørup [this message]
2025-10-29 14:50 ` [PATCH v2] " Stephen Hemminger
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=98CBD80474FA8B44BF855DF32C47DC35F65512@smartserver.smartshare.dk \
--to=mb@smartsharesystems.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=roretzla@linux.microsoft.com \
--cc=stephen@networkplumber.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).