mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Mark Tomlinson <mark.tomlinson@alliedtelesis.co.nz>
Cc: jmaloy@redhat.com, ying.xue@windriver.com, davem@davemloft.net,
	netdev@vger.kernel.org, tipc-discussion@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tipc: Fix recognition of trial period
Date: Fri, 14 Oct 2022 07:40:16 +0000	[thread overview]
Message-ID: <166573321636.24049.11691596559527099656.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221010024613.2951-1-mark.tomlinson@alliedtelesis.co.nz>

Hello:

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

On Mon, 10 Oct 2022 15:46:13 +1300 you wrote:
> The trial period exists until jiffies is after addr_trial_end. But as
> jiffies will eventually overflow, just using time_after will eventually
> give incorrect results. As the node address is set once the trial period
> ends, this can be used to know that we are not in the trial period.
> 
> Fixes: e415577f57f4 ("tipc: correct discovery message handling during address trial period")
> Signed-off-by: Mark Tomlinson <mark.tomlinson@alliedtelesis.co.nz>
> 
> [...]

Here is the summary with links:
  - tipc: Fix recognition of trial period
    https://git.kernel.org/netdev/net/c/28be7ca4fcfd

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



      reply	other threads:[~2022-10-14  7:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-10  2:46 Mark Tomlinson
2022-10-14  7:40 ` 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=166573321636.24049.11691596559527099656.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=jmaloy@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.tomlinson@alliedtelesis.co.nz \
    --cc=netdev@vger.kernel.org \
    --cc=tipc-discussion@lists.sourceforge.net \
    --cc=ying.xue@windriver.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
all inboxes | Powered by JetHome®