[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m2zfyq53wz.fsf@gmail.com>
Date: Mon, 04 Dec 2023 16:27:24 +0000
From: Donald Hunter <donald.hunter@...il.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: netdev@...r.kernel.org, "David S. Miller" <davem@...emloft.net>, Eric
Dumazet <edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>, Jonathan
Corbet <corbet@....net>, linux-doc@...r.kernel.org, Jacob Keller
<jacob.e.keller@...el.com>, donald.hunter@...hat.com
Subject: Re: [PATCH net-next v1 6/6] doc/netlink/specs: Add a spec for tc
Jakub Kicinski <kuba@...nel.org> writes:
> On Thu, 30 Nov 2023 21:49:58 +0000 Donald Hunter wrote:
>> + -
>> + name: app
>> + type: binary # TODO sub-message needs 2+ level deep lookup
>> + sub-message: tca-stats-app-msg
>> + selector: kind
>
> Ugh. Meaning the selector is at a "previous" level of nesting?
That's right. I wonder if we should use a relative syntax like "../kind"
for the selector. Will either need to pass the known attrs to nest
parsing, or pass a resolver instead?
Powered by blists - more mailing lists