From: Jakub Kicinski <kuba@kernel.org>
To: Jiri Pirko <jiri@resnulli.us>
Cc: netdev@vger.kernel.org
Subject: Re: ynl - mutiple policies for one nested attr used in multiple cmds
Date: Fri, 18 Aug 2023 08:55:35 -0700 [thread overview]
Message-ID: <20230818085535.3826f133@kernel.org> (raw)
In-Reply-To: <ZN8tv9bH1Bq8s7SS@nanopsycho>
On Fri, 18 Aug 2023 10:37:19 +0200 Jiri Pirko wrote:
> >I'm not sure if you'll like it but my first choice would be to skip
> >the selector attribute. Put the attributes directly into the message.
> >There is no functional purpose the wrapping serves, right?
>
> I have another variation of a similar problem.
> There might be a different policy for nested attribute for get and set.
> Example nest: DEVLINK_ATTR_PORT_FUNCTION
>
> Any suggestion how to resolve this?
You mean something like:
GET:
[NEST_X]
[ATTR_A]
[ATTR_B]
GET:
[NEST_X]
[ATTR_A]
[ATTR_C]
Where ATTR_A, ATTR_B and ATTR_C are from the same set but depending
on the command the nest can either contain A,C or A,B?
That can happen in legit ways :( I don't have a good solution for it.
next prev parent reply other threads:[~2023-08-18 15:55 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
2023-08-18 8:37 ` Jiri Pirko
2023-08-18 15:55 ` Jakub Kicinski [this message]
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=20230818085535.3826f133@kernel.org \
--to=kuba@kernel.org \
--cc=jiri@resnulli.us \
--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;
as well as URLs for NNTP newsgroup(s).