public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel•org
To: Jian Yang <jianyang.kernel@gmail•com>
Cc: davem@davemloft•net, kuba@kernel•org, netdev@vger•kernel.org,
	maheshb@google•com, jianyang@google•com
Subject: Re: [PATCH net-next v3] net-loopback: set lo dev initial state to UP
Date: Fri, 05 Feb 2021 03:00:08 +0000	[thread overview]
Message-ID: <161249400830.18283.17954804241614751474.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210201233445.2044327-1-jianyang.kernel@gmail.com>

Hello:

This patch was applied to netdev/net-next.git (refs/heads/master):

On Mon,  1 Feb 2021 15:34:45 -0800 you wrote:
> From: Jian Yang <jianyang@google•com>
> 
> Traditionally loopback devices come up with initial state as DOWN for
> any new network-namespace. This would mean that anyone needing this
> device would have to bring this UP by issuing something like 'ip link
> set lo up'. This can be avoided if the initial state is set as UP.
> 
> [...]

Here is the summary with links:
  - [net-next,v3] net-loopback: set lo dev initial state to UP
    https://git.kernel.org/netdev/net-next/c/c9dca822c729

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



  reply	other threads:[~2021-02-05  3:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-01 23:34 [PATCH net-next v3] net-loopback: set lo dev initial state to UP Jian Yang
2021-02-05  3:00 ` patchwork-bot+netdevbpf [this message]
2021-02-09 11:54 ` Petr Machata
2021-02-09 16:23   ` Jakub Kicinski
2021-02-09 17:19     ` Petr Machata
2021-02-09 18:49     ` Mahesh Bandewar (महेश बंडेवार)
2021-02-09 19:04       ` Jakub Kicinski
2021-02-09 19:18         ` Mahesh Bandewar (महेश बंडेवार)
2021-02-09 19:43           ` Jakub Kicinski
2021-02-09 19:06       ` Ido Schimmel
2021-02-09 19:19         ` Mahesh Bandewar (महेश बंडेवार)

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=161249400830.18283.17954804241614751474.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel$(echo .)org \
    --cc=davem@davemloft$(echo .)net \
    --cc=jianyang.kernel@gmail$(echo .)com \
    --cc=jianyang@google$(echo .)com \
    --cc=kuba@kernel$(echo .)org \
    --cc=maheshb@google$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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