netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Suresh Kumar <surkumar@redhat.com>
Cc: j.vosburgh@gmail.com, vfalico@gmail.com, andy@greyhouse.net,
	davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, suresh2514@gmail.com
Subject: Re: [PATCH] net: bonding: debug: avoid printing debug logs when bond is not notifying peers
Date: Mon, 13 Dec 2021 15:00:10 +0000	[thread overview]
Message-ID: <163940761077.26947.18066231032018487872.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211213054709.158550-1-suresh2514@gmail.com>

Hello:

This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:

On Mon, 13 Dec 2021 11:17:09 +0530 you wrote:
> Currently "bond_should_notify_peers: slave ..." messages are printed whenever
> "bond_should_notify_peers" function is called.
> 
> +++
> Dec 12 12:33:26 node1 kernel: bond0: bond_should_notify_peers: slave enp0s25
> Dec 12 12:33:26 node1 kernel: bond0: bond_should_notify_peers: slave enp0s25
> Dec 12 12:33:26 node1 kernel: bond0: bond_should_notify_peers: slave enp0s25
> Dec 12 12:33:26 node1 kernel: bond0: (slave enp0s25): Received LACPDU on port 1
> Dec 12 12:33:26 node1 kernel: bond0: (slave enp0s25): Rx Machine: Port=1, Last State=6, Curr State=6
> Dec 12 12:33:26 node1 kernel: bond0: (slave enp0s25): partner sync=1
> Dec 12 12:33:26 node1 kernel: bond0: bond_should_notify_peers: slave enp0s25
> Dec 12 12:33:26 node1 kernel: bond0: bond_should_notify_peers: slave enp0s25
> Dec 12 12:33:26 node1 kernel: bond0: bond_should_notify_peers: slave enp0s25
> ...
> Dec 12 12:33:30 node1 kernel: bond0: bond_should_notify_peers: slave enp0s25
> Dec 12 12:33:30 node1 kernel: bond0: bond_should_notify_peers: slave enp0s25
> Dec 12 12:33:30 node1 kernel: bond0: (slave enp4s3): Received LACPDU on port 2
> Dec 12 12:33:30 node1 kernel: bond0: (slave enp4s3): Rx Machine: Port=2, Last State=6, Curr State=6
> Dec 12 12:33:30 node1 kernel: bond0: (slave enp4s3): partner sync=1
> Dec 12 12:33:30 node1 kernel: bond0: bond_should_notify_peers: slave enp0s25
> Dec 12 12:33:30 node1 kernel: bond0: bond_should_notify_peers: slave enp0s25
> Dec 12 12:33:30 node1 kernel: bond0: bond_should_notify_peers: slave enp0s25
> +++
> 
> [...]

Here is the summary with links:
  - net: bonding: debug: avoid printing debug logs when bond is not notifying peers
    https://git.kernel.org/netdev/net-next/c/fee32de284ac

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



      reply	other threads:[~2021-12-13 15:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-13  5:47 [PATCH] net: bonding: debug: avoid printing debug logs when bond is not notifying peers Suresh Kumar
2021-12-13 15: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=163940761077.26947.18066231032018487872.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andy@greyhouse.net \
    --cc=davem@davemloft.net \
    --cc=j.vosburgh@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=suresh2514@gmail.com \
    --cc=surkumar@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).