From: Jakub Kicinski <kuba@kernel.org>
To: "Remy D. Farley" <one-d-wide@protonmail.com>
Cc: Donald Hunter <donald.hunter@gmail.com>, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2] doc/netlink: rt-link: fix binary attributes marked as strings
Date: Thu, 28 May 2026 17:34:35 -0700 [thread overview]
Message-ID: <20260528173435.368d8267@kernel.org> (raw)
In-Reply-To: <20260526230321.594068-1-one-d-wide@protonmail.com>
On Tue, 26 May 2026 23:04:56 +0000 Remy D. Farley wrote:
> These link-attrs attributes were previously marked as strings:
>
> - wireless - struct iw_event
> - protinfo - a nest of ifla6-attrs or linkinfo-brport-attrs
> - cost, priority - unused
> -
> name: cost
> - type: string
> + type: binary
type: unused
is a thing, should we use it instead of binary?
IIRC it's expected to never exist in messages but to still output
an entry into uAPI, which I think matches the situation here.
Sorry, should have looked closer at v1.
next prev parent reply other threads:[~2026-05-29 0:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-26 23:04 [PATCH net-next v2] doc/netlink: rt-link: fix binary attributes marked as strings Remy D. Farley
2026-05-29 0:34 ` Jakub Kicinski [this message]
2026-05-29 12:10 ` Remy D. Farley
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=20260528173435.368d8267@kernel.org \
--to=kuba@kernel.org \
--cc=donald.hunter@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=one-d-wide@protonmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.