From: Jakub Kicinski <kuba@kernel.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: James Prestwood <prestwoj@gmail.com>, netdev@vger.kernel.org
Subject: Re: [RFC 1/1] net: move IFF_LIVE_ADDR_CHANGE to public flag
Date: Wed, 10 Aug 2022 10:36:01 -0700 [thread overview]
Message-ID: <20220810103601.0dccbc63@kernel.org> (raw)
In-Reply-To: <9ec77cf1ffaa29aedd57c29ac77b525d0e700acf.camel@sipsolutions.net>
On Wed, 10 Aug 2022 19:17:19 +0200 Johannes Berg wrote:
> Thinking about that now, maybe it's not _that_ bad? Especially given
> that "live" can mean different things (as discussed here), and for
> wireless that doesn't necessarily mean IFF_UP, but rather something like
> "IFF_UP + not active".
>
> Jakub, what do you think?
Agreed, even tho the concept of a live address change seems generic
the implications and definition of "live" are very area specific.
Let's handwave that nl80211 is a subordinate API of RT netlink :)
next prev parent reply other threads:[~2022-08-10 17:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 17:43 [RFC 0/1] Move IFF_LIVE_ADDR_CHANGE to public flag James Prestwood
2022-08-04 17:43 ` [RFC 1/1] net: move " James Prestwood
2022-08-04 17:59 ` Stephen Hemminger
2022-08-04 19:29 ` James Prestwood
2022-08-04 18:43 ` Jakub Kicinski
2022-08-04 19:23 ` James Prestwood
2022-08-04 19:49 ` James Prestwood
2022-08-09 19:04 ` Johannes Berg
2022-08-10 16:26 ` James Prestwood
2022-08-10 17:17 ` Johannes Berg
2022-08-10 17:36 ` Jakub Kicinski [this message]
2022-08-10 19:35 ` James Prestwood
2022-08-04 20:49 ` [RFC 0/1] Move " Andrew Lunn
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=20220810103601.0dccbc63@kernel.org \
--to=kuba@kernel.org \
--cc=johannes@sipsolutions.net \
--cc=netdev@vger.kernel.org \
--cc=prestwoj@gmail.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 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).