[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANn89iLvC0H+eb1q1c9X6M1Cr296oLTWYyBhqTAyGW_BusHA_A@mail.gmail.com>
Date: Thu, 7 Nov 2024 14:37:42 +0100
From: Eric Dumazet <edumazet@...gle.com>
To: Xiao Liang <shaw.leon@...il.com>
Cc: netdev@...r.kernel.org, linux-kselftest@...r.kernel.org,
Kuniyuki Iwashima <kuniyu@...zon.com>, Jakub Kicinski <kuba@...nel.org>,
"David S. Miller" <davem@...emloft.net>, David Ahern <dsahern@...nel.org>,
Paolo Abeni <pabeni@...hat.com>, Ido Schimmel <idosch@...dia.com>,
Andrew Lunn <andrew+netdev@...n.ch>, Simon Horman <horms@...nel.org>,
Donald Hunter <donald.hunter@...il.com>, Shuah Khan <shuah@...nel.org>,
Jiri Pirko <jiri@...nulli.us>, Hangbin Liu <liuhangbin@...il.com>
Subject: Re: [PATCH net-next v2 5/8] net: ip_gre: Add netns_atomic module parameter
On Thu, Nov 7, 2024 at 2:30 PM Xiao Liang <shaw.leon@...il.com> wrote:
>
> If set to true, create device in target netns (when different from
> link-netns) without netns change, and use current netns as link-netns
> if not specified explicitly.
>
Sorry, module parameters are not going to fly.
Instead, add new rtnetlink attributes ?
Powered by blists - more mailing lists