From: Bruce Richardson <bruce.richardson@intel.com>
To: "Burakov, Anatoly" <anatoly.burakov@intel.com>
Cc: "Medvedkin, Vladimir" <vladimir.medvedkin@intel.com>,
<dev@dpdk.org>, Kevin Liu <kevinx.liu@intel.com>,
Qi Zhang <qi.z.zhang@intel.com>
Subject: Re: [PATCH v2 3/3] net/ice: do not include private headers in testpmd
Date: Thu, 15 Oct 2026 16:21:10 +0100 [thread overview]
Message-ID: <atDvZiRddrDI_mJD@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <ef450e1d-34ca-4876-b94c-6a3dcd885f19@intel.com>
On Thu, Oct 15, 2026 at 05:00:38PM +0200, Burakov, Anatoly wrote:
> On 10/15/2026 4:52 PM, Medvedkin, Vladimir wrote:
> > Hi Anatoly,
> >
> > One nit: the buffer must be allocated with malloc, could you please
> > reflect this information in doxygen comments?
>
> @Bruce
>
> Perhaps this can be fixed on apply?
>
> diff --git a/drivers/net/intel/ice/rte_pmd_ice.h
> b/drivers/net/intel/ice/rte_pmd_ice.h
> index dccfdcd5f4..881dc4cc56 100644
> --- a/drivers/net/intel/ice/rte_pmd_ice.h
> +++ b/drivers/net/intel/ice/rte_pmd_ice.h
> @@ -27,8 +27,9 @@ extern "C" {
> * @param port
> * The port identifier of the Ethernet device.
> * @param buff
> - * Pointer to an allocated buffer. On success, it may be replaced by a
> - * newly allocated buffer; the caller must free the resulting buffer.
> + * Pointer to a `malloc()`-allocated buffer. On success, it will be freed
> by
> + * `free()` and replaced by a newly `malloc()`-allocated buffer; the
> caller
> + * must free the resulting buffer.
That is very strange behaviour! That looks like something a future patch
should fix, but ok to change the documentation on apply here.
/Bruce
next prev parent reply other threads:[~2026-10-15 15:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 20:34 [PATCH] net/ixgbe: avoid private driver include in testpmd Thomas Monjalon
2026-10-15 8:53 ` Burakov, Anatoly
2026-10-15 9:13 ` Thomas Monjalon
2026-10-15 10:41 ` Burakov, Anatoly
2026-10-15 11:18 ` David Marchand
2026-10-15 11:21 ` Burakov, Anatoly
2026-10-15 11:50 ` Thomas Monjalon
2026-10-15 14:01 ` Burakov, Anatoly
2026-10-15 14:21 ` [PATCH v2 1/3] " Anatoly Burakov
2026-10-15 14:21 ` [PATCH v2 2/3] net/iavf: do not include private headers " Anatoly Burakov
2026-10-15 14:33 ` Bruce Richardson
2026-10-15 14:45 ` Medvedkin, Vladimir
2026-10-15 14:21 ` [PATCH v2 3/3] net/ice: " Anatoly Burakov
2026-10-15 14:36 ` Bruce Richardson
2026-10-15 14:39 ` Bruce Richardson
2026-10-15 14:52 ` Medvedkin, Vladimir
2026-10-15 15:00 ` Burakov, Anatoly
2026-10-15 15:21 ` Bruce Richardson [this message]
2026-10-15 15:29 ` Burakov, Anatoly
2026-10-15 14:44 ` [PATCH v2 1/3] net/ixgbe: avoid private driver include " Medvedkin, Vladimir
2026-10-15 17:09 ` Bruce Richardson
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=atDvZiRddrDI_mJD@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=kevinx.liu@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=vladimir.medvedkin@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