From: Jakub Kicinski <kuba@kernel.org>
To: Jamal Hadi Salim <jhs@mojatatu.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
stephen@networkplumber.org, dsahern@gmail.com,
netdev@vger.kernel.org
Subject: Re: [PATCH iproute2] genl: print caps for all families
Date: Fri, 24 Feb 2023 09:10:55 -0800 [thread overview]
Message-ID: <20230224091055.1a63e08e@kernel.org> (raw)
In-Reply-To: <CAM0EoMm9NyE7nJZ4ktntNMUsCQkyEuVyR5f_E7TgiKNCo15a3A@mail.gmail.com>
On Fri, 24 Feb 2023 10:22:56 -0500 Jamal Hadi Salim wrote:
> After a couple of sips of some unknown drink: I think we can get rid
> of ctrl_v altogether as a param to the printers and we should be good
> (it would work for events as well).
Do you mean to always interpret the flags? FWIW I think that should
be fine, old kernels just don't set those flags so I'm not sure why
we're gating interpreting them with the version.
next prev parent reply other threads:[~2023-02-24 17:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 1:52 [PATCH iproute2] genl: print caps for all families Jakub Kicinski
2023-02-24 1:57 ` Jakub Kicinski
2023-02-24 8:33 ` Johannes Berg
2023-02-24 15:15 ` Jamal Hadi Salim
2023-02-24 15:22 ` Jamal Hadi Salim
2023-02-24 17:10 ` Jakub Kicinski [this message]
2023-02-24 17:46 ` Jamal Hadi Salim
2023-02-24 18:30 ` Jakub Kicinski
2023-02-24 3:27 ` Stephen Hemminger
2023-02-24 17:11 ` Jakub Kicinski
2023-02-24 17:47 ` Jamal Hadi Salim
2023-02-24 18:29 ` Jakub Kicinski
2023-02-24 22:33 ` Stephen Hemminger
2023-02-25 0:56 ` Jakub Kicinski
2023-02-25 17:21 ` Jamal Hadi Salim
-- strict thread matches above, loose matches on Subject: below --
2023-02-25 0:37 Jakub Kicinski
2023-02-25 16:41 ` Jamal Hadi Salim
2023-03-04 2:20 ` patchwork-bot+netdevbpf
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=20230224091055.1a63e08e@kernel.org \
--to=kuba@kernel.org \
--cc=dsahern@gmail.com \
--cc=jhs@mojatatu.com \
--cc=johannes@sipsolutions.net \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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).