Linux Netfilter development
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Ratheesh Kannoth <rkannoth@marvell.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] libmnl: add MNL_TYPE_UARR for devlink u64 array attributes
Date: Tue, 23 Jun 2026 11:48:16 +0200	[thread overview]
Message-ID: <ajpWYAQ1Od2ilpAk@chamomile> (raw)
In-Reply-To: <20260623043755.2435685-1-rkannoth@marvell.com>

On Tue, Jun 23, 2026 at 10:07:55AM +0530, Ratheesh Kannoth wrote:
> Add MNL_TYPE_UARR (129) to enum mnl_attr_data_type to match
> DEVLINK_VAR_ATTR_TYPE_U64_ARRAY in the kernel. That type represents
> devlink param values encoded as a nested list of u64 attributes in
> DEVLINK_ATTR_PARAM_VALUE_DATA, allowing drivers and userspace to
> exchange variable-length u64/u32 arrays (e.g. multi-value devlink params).
> 
> Signed-off-by: Ratheesh Kannoth <rkannoth@marvell.com>
> ---
>  include/libmnl/libmnl.h | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/include/libmnl/libmnl.h b/include/libmnl/libmnl.h
> index 0331da7..078d517 100644
> --- a/include/libmnl/libmnl.h
> +++ b/include/libmnl/libmnl.h
> @@ -133,6 +133,7 @@ enum mnl_attr_data_type {
>  	MNL_TYPE_NESTED_COMPAT,
>  	MNL_TYPE_NUL_STRING,
>  	MNL_TYPE_BINARY,
> +	MNL_TYPE_UARR = 129,

Why 129?

>  	MNL_TYPE_MAX,
>  };
>  
> -- 
> 2.43.0
> 
> 

  reply	other threads:[~2026-06-23  9:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-23  4:37 [PATCH] libmnl: add MNL_TYPE_UARR for devlink u64 array attributes Ratheesh Kannoth
2026-06-23  9:48 ` Pablo Neira Ayuso [this message]
2026-06-23 10:33   ` RE:: " Ratheesh Kannoth
2026-06-23 11:01     ` : " Pablo Neira Ayuso
2026-06-23 11:08       ` [EXTERNAL] " Ratheesh Kannoth

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=ajpWYAQ1Od2ilpAk@chamomile \
    --to=pablo@netfilter.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=rkannoth@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox