All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Kubalewski@ci.codeaurora.org, Arkadiusz <arkadiusz.kubalewski@intel.com>
Cc: netdev@vger.kernel.org, vadim.fedorenko@linux.dev,
	jiri@resnulli.us, davem@davemloft.net, rrameshbabu@nvidia.com,
	linux-kernel@vger.kernel.org, pabeni@redhat.com, kuba@kernel.org,
	mschmidt@redhat.com
Subject: Re: [PATCH net v2] dpll: fix dpll_pin_on_pin_register() for multiple parent pins
Date: Thu, 25 Apr 2024 15:40:30 +0000	[thread overview]
Message-ID: <171405963002.10966.12819145929067304526.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240424101636.1491424-1-arkadiusz.kubalewski@intel.com>

Hello:

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

On Wed, 24 Apr 2024 12:16:36 +0200 you wrote:
> In scenario where pin is registered with multiple parent pins via
> dpll_pin_on_pin_register(..), all belonging to the same dpll device.
> A second call to dpll_pin_on_pin_unregister(..) would cause a call trace,
> as it tries to use already released registration resources (due to fix
> introduced in b446631f355e). In this scenario pin was registered twice,
> so resources are not yet expected to be release until each registered
> pin/pin pair is unregistered.
> 
> [...]

Here is the summary with links:
  - [net,v2] dpll: fix dpll_pin_on_pin_register() for multiple parent pins
    https://git.kernel.org/netdev/net/c/38d7b94e81d0

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-04-25 15:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-24 10:16 [PATCH net v2] dpll: fix dpll_pin_on_pin_register() for multiple parent pins Arkadiusz Kubalewski
2024-04-24 14:44 ` Jiri Pirko
2024-04-25 15: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=171405963002.10966.12819145929067304526.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=Kubalewski@ci.codeaurora.org \
    --cc=arkadiusz.kubalewski@intel.com \
    --cc=davem@davemloft.net \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mschmidt@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rrameshbabu@nvidia.com \
    --cc=vadim.fedorenko@linux.dev \
    /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.