Re: [PATCHv3 net-next 2/2] ynl: support binary/u32 sub-type for indexed-array

[Hangbin Liu <liuhangbin@gmail.com>]

On Mon, Apr 01, 2024 at 09:43:31PM -0700, Jakub Kicinski wrote:
> I think that elsewhere in the doc we use [SOMETHING] to mean
> TLV of type SOMETHING, here MEMBER1/2 are presumably just
> payloads of each ENTRY? Maybe this is better:
> 
>   [SOME-OTHER-ATTR]
>   [ARRAY-ATTR]
>     [ENTRY u32]
>     [ENTRY u32]
> 

Thanks, I will update the doc.
> ?
> 
> >  type-value
> >  ~~~~~~~~~~
> > diff --git a/tools/net/ynl/lib/ynl.py b/tools/net/ynl/lib/ynl.py
> > index e5ad415905c7..aa7077cffe74 100644
> > --- a/tools/net/ynl/lib/ynl.py
> > +++ b/tools/net/ynl/lib/ynl.py
> > @@ -640,6 +640,11 @@ class YnlFamily(SpecFamily):
> >              if attr_spec["sub-type"] == 'nest':
> >                  subattrs = self._decode(NlAttrs(item.raw), attr_spec['nested-attributes'])
> >                  decoded.append({ item.type: subattrs })
> > +            elif attr_spec["sub-type"] == 'binary' or attr_spec["sub-type"] == 'u32':
> > +                subattrs = item.as_bin()
> 
> Are you sure that as_bin() will work for all u32s?
> Or just when there's a hint...

I didn't check other subsystem. For bonding only, if we don't have the hint.
e.g.

  -
    name: arp-ip-target
    type: indexed-array
    sub-type: u32

The result will looks like:

    "arp-ip-target": [
      "c0a80101",
      "c0a80102"
    ],

Which looks good to me. Do you have other suggestion?

Thanks
Hangbin