All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Lukasz Majewski <lukma@denx.de>
Cc: kuba@kernel.org, netdev@vger.kernel.org, pabeni@redhat.com,
	edumazet@google.com, olteanv@gmail.com, davem@davemloft.net,
	o.rempel@pengutronix.de, Tristram.Ha@microchip.com,
	bigeasy@linutronix.de, r-gunasekaran@ti.com, horms@kernel.org,
	n.zhandarovich@fintech.ru, m-karicheri2@ti.com,
	Arvid.Brodin@xdin.com, dan.carpenter@linaro.org,
	ricardo@marliere.net, casper.casan@gmail.com,
	linux-kernel@vger.kernel.org
Subject: Re: [net PATCH v2] hsr: Simplify code for announcing HSR nodes timer setup
Date: Thu, 09 May 2024 02:00:29 +0000	[thread overview]
Message-ID: <171522002913.32544.11720704507207514169.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240507111214.3519800-1-lukma@denx.de>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Tue,  7 May 2024 13:12:14 +0200 you wrote:
> Up till now the code to start HSR announce timer, which triggers sending
> supervisory frames, was assuming that hsr_netdev_notify() would be called
> at least twice for hsrX interface. This was required to have different
> values for old and current values of network device's operstate.
> 
> This is problematic for a case where hsrX interface is already in the
> operational state when hsr_netdev_notify() is called, so timer is not
> configured to trigger and as a result the hsrX is not sending supervisory
> frames to HSR ring.
> 
> [...]

Here is the summary with links:
  - [net,v2] hsr: Simplify code for announcing HSR nodes timer setup
    https://git.kernel.org/netdev/net/c/4893b8b3ef8d

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



      parent reply	other threads:[~2024-05-09  2:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-07 11:12 [net PATCH v2] hsr: Simplify code for announcing HSR nodes timer setup Lukasz Majewski
2024-05-08 10:14 ` Simon Horman
2024-05-09  2: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=171522002913.32544.11720704507207514169.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=Arvid.Brodin@xdin.com \
    --cc=Tristram.Ha@microchip.com \
    --cc=bigeasy@linutronix.de \
    --cc=casper.casan@gmail.com \
    --cc=dan.carpenter@linaro.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukma@denx.de \
    --cc=m-karicheri2@ti.com \
    --cc=n.zhandarovich@fintech.ru \
    --cc=netdev@vger.kernel.org \
    --cc=o.rempel@pengutronix.de \
    --cc=olteanv@gmail.com \
    --cc=pabeni@redhat.com \
    --cc=r-gunasekaran@ti.com \
    --cc=ricardo@marliere.net \
    /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.