All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Andy Ren <andy.ren@getcruise.com>
Cc: netdev@vger.kernel.org, richardbgobert@gmail.com,
	davem@davemloft.net, wsa+renesas@sang-engineering.com,
	edumazet@google.com, petrm@nvidia.com, kuba@kernel.org,
	pabeni@redhat.com, corbet@lwn.net, andrew@lunn.ch,
	dsahern@gmail.com, sthemmin@microsoft.com, idosch@idosch.org,
	sridhar.samudrala@intel.com, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, roman.gushchin@linux.dev
Subject: Re: [PATCH net-next v3] net/core: Allow live renaming when an interface is up
Date: Wed, 09 Nov 2022 14:00:15 +0000	[thread overview]
Message-ID: <166800241569.22395.12507776446911406225.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221107174242.1947286-1-andy.ren@getcruise.com>

Hello:

This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:

On Mon,  7 Nov 2022 09:42:42 -0800 you wrote:
> Allow a network interface to be renamed when the interface
> is up.
> 
> As described in the netconsole documentation [1], when netconsole is
> used as a built-in, it will bring up the specified interface as soon as
> possible. As a result, user space will not be able to rename the
> interface since the kernel disallows renaming of interfaces that are
> administratively up unless the 'IFF_LIVE_RENAME_OK' private flag was set
> by the kernel.
> 
> [...]

Here is the summary with links:
  - [net-next,v3] net/core: Allow live renaming when an interface is up
    https://git.kernel.org/netdev/net-next/c/bd039b5ea2a9

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2022-11-09 14:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-07 17:42 [PATCH net-next v3] net/core: Allow live renaming when an interface is up Andy Ren
2022-11-08 11:02 ` Ido Schimmel
2022-11-08 15:30 ` David Ahern
2022-11-09 14:00 ` patchwork-bot+netdevbpf [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=166800241569.22395.12507776446911406225.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=andy.ren@getcruise.com \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=dsahern@gmail.com \
    --cc=edumazet@google.com \
    --cc=idosch@idosch.org \
    --cc=kuba@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=petrm@nvidia.com \
    --cc=richardbgobert@gmail.com \
    --cc=roman.gushchin@linux.dev \
    --cc=sridhar.samudrala@intel.com \
    --cc=sthemmin@microsoft.com \
    --cc=wsa+renesas@sang-engineering.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.