All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Tapio Reijonen <tapio.reijonen@vaisala.com>
Cc: woojung.huh@microchip.com, UNGLinuxDriver@microchip.com,
	andrew@lunn.ch, olteanv@gmail.com, davem@davemloft.net,
	edumazet@kernel.org, kuba@kernel.org, pabeni@redhat.com,
	arun.ramadoss@microchip.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, Tristram.Ha@microchip.com,
	stable@vger.kernel.org
Subject: Re: [PATCH net] net: dsa: microchip: initialize the IRQ access mutex
Date: Tue, 10 Nov 2026 14:20:05 +0000	[thread overview]
Message-ID: <179432040518.3989458.1694702089176046934.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261104-ksz-irq-mutex-init-v1-1-e3bb7d9dbd80@vaisala.com>

Hello:

This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Wed, 04 Nov 2026 07:58:35 +0000 you wrote:
> ksz_switch_register() initializes dev_mutex, regmap_mutex, alu_mutex and
> vlan_mutex but not lock_irq, which the IRQ chip takes in its bus lock
> callbacks on every mask and unmask of a switch interrupt, and the PTP
> code takes the same way. The zeroed mutex happens to work on the
> uncontended fast path, but with CONFIG_DEBUG_MUTEXES the first lock,
> from the IRQ domain mapping during probe, warns:
> 
> [...]

Here is the summary with links:
  - [net] net: dsa: microchip: initialize the IRQ access mutex
    https://git.kernel.org/netdev/net/c/ba1dc196502f

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



      parent reply	other threads:[~2026-11-10 14:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-04  7:58 [PATCH net] net: dsa: microchip: initialize the IRQ access mutex Tapio Reijonen
2026-11-06 10:47 ` Daniel Machon
2026-11-10 14: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=179432040518.3989458.1694702089176046934.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=Tristram.Ha@microchip.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=andrew@lunn.ch \
    --cc=arun.ramadoss@microchip.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=pabeni@redhat.com \
    --cc=stable@vger.kernel.org \
    --cc=tapio.reijonen@vaisala.com \
    --cc=woojung.huh@microchip.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 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.