From: Jakub Kicinski <kuba@kernel.org>
To: Florent Fourcot <florent.fourcot@wifirst.fr>
Cc: netdev@vger.kernel.org, cong.wang@bytedance.com,
edumazet@google.com, Jiri Pirko <jiri@mellanox.com>,
Brian Baboch <brian.baboch@wifirst.fr>
Subject: Re: [PATCH net v2] rtnetlink: enable alt_ifname for setlink/newlink
Date: Fri, 1 Apr 2022 15:09:08 -0700 [thread overview]
Message-ID: <20220401150908.356a0db3@kernel.org> (raw)
In-Reply-To: <1250f3a0-9ed3-cfad-ba93-6b16cad5dcf5@wifirst.fr>
On Fri, 1 Apr 2022 23:02:39 +0200 Florent Fourcot wrote:
> I don't really care about getting this into stable, so I will resubmit
> for net-next when opened.
> Should I drop "Fixes" tag?
Yup! No fixes tag if it's going in to net-next.
> Alternatives ifname feature never worked for setlink/newlink,
> but 76c9ac0ee878 claimed it was.
I wonder what the story was there. I think it "works" in that ip link
accept altnames, but IIUC that's because it does a get first and
resolves the ifindex.
prev parent reply other threads:[~2022-04-01 22:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 15:39 [PATCH net v2] rtnetlink: enable alt_ifname for setlink/newlink Florent Fourcot
2022-04-01 17:43 ` Jakub Kicinski
2022-04-01 21:02 ` Florent Fourcot
2022-04-01 22:09 ` Jakub Kicinski [this message]
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=20220401150908.356a0db3@kernel.org \
--to=kuba@kernel.org \
--cc=brian.baboch@wifirst.fr \
--cc=cong.wang@bytedance.com \
--cc=edumazet@google.com \
--cc=florent.fourcot@wifirst.fr \
--cc=jiri@mellanox.com \
--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).