From: Jiri Pirko <jiri@resnulli.us>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org
Subject: Re: ynl - mutiple policies for one nested attr used in multiple cmds
Date: Tue, 8 Aug 2023 09:38:47 +0200 [thread overview]
Message-ID: <ZNHxBxSJboYfDA0V@nanopsycho> (raw)
In-Reply-To: <20230807102406.19a131d3@kernel.org>
Mon, Aug 07, 2023 at 07:24:06PM CEST, kuba@kernel.org wrote:
>On Mon, 7 Aug 2023 19:12:30 +0200 Jiri Pirko wrote:
>> >How does the situation look with the known user apps? Is anyone
>> >that we know of putting attributes into dump requests?
>>
>> I'm not aware of that.
>
>I vote to risk it and skip the nest, then :)
Okay, will implement strict parsing for dumps, treating attributes as
selectors. Cool.
next prev parent reply other threads:[~2023-08-08 18:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-04 17:29 ynl - mutiple policies for one nested attr used in multiple cmds Jiri Pirko
2023-08-04 19:58 ` Jakub Kicinski
2023-08-05 6:33 ` Jiri Pirko
2023-08-07 17:03 ` Jakub Kicinski
2023-08-07 17:12 ` Jiri Pirko
2023-08-07 17:24 ` Jakub Kicinski
2023-08-08 7:38 ` Jiri Pirko [this message]
2023-08-18 8:37 ` Jiri Pirko
2023-08-18 15:55 ` Jakub Kicinski
2023-08-18 18:11 ` Jiri Pirko
2023-08-18 20:24 ` Jakub Kicinski
2023-08-21 11:16 ` Jiri Pirko
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=ZNHxBxSJboYfDA0V@nanopsycho \
--to=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.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