From: patchwork-bot+netdevbpf@kernel.org
To: Jay Vosburgh <jay.vosburgh@canonical.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org, jtoppins@redhat.com,
vfalico@gmail.com, andy@greyhouse.net
Subject: Re: [PATCH net] veth: Add updating of trans_start
Date: Fri, 17 Jun 2022 10:40:14 +0000 [thread overview]
Message-ID: <165546241430.18293.16871375971208743351.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <9088.1655407590@famine>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Thu, 16 Jun 2022 12:26:30 -0700 you wrote:
> Since commit 21a75f0915dd ("bonding: Fix ARP monitor validation"),
> the bonding ARP / ND link monitors depend on the trans_start time to
> determine link availability. NETIF_F_LLTX drivers must update trans_start
> directly, which veth does not do. This prevents use of the ARP or ND link
> monitors with veth interfaces in a bond.
>
> Resolve this by having veth_xmit update the trans_start time.
>
> [...]
Here is the summary with links:
- [net] veth: Add updating of trans_start
https://git.kernel.org/netdev/net/c/e66e257a5d83
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-06-17 10:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 19:26 [PATCH net] veth: Add updating of trans_start Jay Vosburgh
2022-06-17 10:40 ` patchwork-bot+netdevbpf [this message]
2022-06-17 15:45 ` Jakub Kicinski
2022-06-17 16:42 ` Jay Vosburgh
2022-06-17 19:44 ` Jakub Kicinski
2022-06-18 0:27 ` Jay Vosburgh
2022-06-18 0:55 ` Jakub Kicinski
2022-06-21 19:52 ` Jakub Kicinski
2022-06-22 1:42 ` Jay Vosburgh
2022-06-22 4:38 ` Jakub Kicinski
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=165546241430.18293.16871375971208743351.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jay.vosburgh@canonical.com \
--cc=jtoppins@redhat.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vfalico@gmail.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 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).