From: patchwork-bot+netdevbpf@kernel.org
To: Jonathan Toppins <jtoppins@redhat.com>
Cc: netdev@vger.kernel.org, j.vosburgh@gmail.com, vfalico@gmail.com,
andy@greyhouse.net, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, corbet@lwn.net,
maheshb@google.com, jarod@redhat.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 1/2] Documentation: bonding: update miimon default to 100
Date: Fri, 02 Dec 2022 11:20:17 +0000 [thread overview]
Message-ID: <166998001717.12503.6133600119187941184.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <4c3f4f0b8f4a8cd3c104d58c106b97ce5f180bc1.1669839127.git.jtoppins@redhat.com>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Wed, 30 Nov 2022 15:12:06 -0500 you wrote:
> With commit c1f897ce186a ("bonding: set default miimon value for non-arp
> modes if not set") the miimon default was changed from zero to 100 if
> arp_interval is also zero. Document this fact in bonding.rst.
>
> Fixes: c1f897ce186a ("bonding: set default miimon value for non-arp modes if not set")
> Signed-off-by: Jonathan Toppins <jtoppins@redhat.com>
>
> [...]
Here is the summary with links:
- [net-next,1/2] Documentation: bonding: update miimon default to 100
https://git.kernel.org/netdev/net-next/c/f036b97da67f
- [net-next,2/2] Documentation: bonding: correct xmit hash steps
https://git.kernel.org/netdev/net-next/c/95cce3fae4d9
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-12-02 11:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 20:12 [PATCH net-next 1/2] Documentation: bonding: update miimon default to 100 Jonathan Toppins
2022-11-30 20:12 ` [PATCH net-next 2/2] Documentation: bonding: correct xmit hash steps Jonathan Toppins
2022-12-02 11: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=166998001717.12503.6133600119187941184.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andy@greyhouse.net \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=j.vosburgh@gmail.com \
--cc=jarod@redhat.com \
--cc=jtoppins@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maheshb@google.com \
--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