From: patchwork-bot+netdevbpf@kernel.org
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: netdev@vger.kernel.org, andrew@lunn.ch, vivien.didelot@gmail.com,
f.fainelli@gmail.com, olteanv@gmail.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com
Subject: Re: [PATCH v2 net-next] net: linkwatch: only report IF_OPER_LOWERLAYERDOWN if iflink is actually down
Date: Wed, 16 Nov 2022 10:00:16 +0000 [thread overview]
Message-ID: <166859281653.28317.17051631605087933356.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221114144256.1908806-1-vladimir.oltean@nxp.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Mon, 14 Nov 2022 16:42:56 +0200 you wrote:
> RFC 2863 says:
>
> The lowerLayerDown state is also a refinement on the down state.
> This new state indicates that this interface runs "on top of" one or
> more other interfaces (see ifStackTable) and that this interface is
> down specifically because one or more of these lower-layer interfaces
> are down.
>
> [...]
Here is the summary with links:
- [v2,net-next] net: linkwatch: only report IF_OPER_LOWERLAYERDOWN if iflink is actually down
https://git.kernel.org/netdev/net-next/c/8c55facecd7a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-11-16 10:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 14:42 [PATCH v2 net-next] net: linkwatch: only report IF_OPER_LOWERLAYERDOWN if iflink is actually down Vladimir Oltean
2022-11-16 10: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=166859281653.28317.17051631605087933356.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=vivien.didelot@gmail.com \
--cc=vladimir.oltean@nxp.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.