From: patchwork-bot+netdevbpf@kernel.org
To: Hangbin Liu <liuhangbin@gmail.com>
Cc: netdev@vger.kernel.org, j.vosburgh@gmail.com, vfalico@gmail.com,
andy@greyhouse.net, jarod@redhat.com, kuba@kernel.org,
jiri@resnulli.us, davem@davemloft.net, dkirjanov@suse.de,
dsahern@gmail.com, jay.vosburgh@canonical.com
Subject: Re: [PATCHv4 net-next] Bonding: add arp_missed_max option
Date: Tue, 30 Nov 2021 12:20:09 +0000 [thread overview]
Message-ID: <163827480999.28928.7861812683592037856.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211130042948.1629239-1-liuhangbin@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Tue, 30 Nov 2021 12:29:47 +0800 you wrote:
> Currently, we use hard code number to verify if we are in the
> arp_interval timeslice. But some user may want to reduce/extend
> the verify timeslice. With the similar team option 'missed_max'
> the uers could change that number based on their own environment.
>
> Acked-by: Jay Vosburgh <jay.vosburgh@canonical.com>
> Signed-off-by: Hangbin Liu <liuhangbin@gmail.com>
>
> [...]
Here is the summary with links:
- [PATCHv4,net-next] Bonding: add arp_missed_max option
https://git.kernel.org/netdev/net-next/c/5944b5abd864
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:[~2021-11-30 12:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-30 4:29 [PATCHv4 net-next] Bonding: add arp_missed_max option Hangbin Liu
2021-11-30 4:29 ` [PATCHv4 iproute2-next] bond: " Hangbin Liu
2021-12-03 17:30 ` patchwork-bot+netdevbpf
2021-11-30 12:20 ` 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=163827480999.28928.7861812683592037856.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=dkirjanov@suse.de \
--cc=dsahern@gmail.com \
--cc=j.vosburgh@gmail.com \
--cc=jarod@redhat.com \
--cc=jay.vosburgh@canonical.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=liuhangbin@gmail.com \
--cc=netdev@vger.kernel.org \
--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 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.