mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Colin Foster <colin.foster@in-advantage.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	andrew@lunn.ch, kuba@kernel.org, davem@davemloft.net,
	UNGLinuxDriver@microchip.com, alexandre.belloni@bootlin.com,
	claudiu.manoil@nxp.com, vladimir.oltean@nxp.com
Subject: Re: [PATCH v1 net 0/1] ocelot stats mutex fix
Date: Thu, 10 Feb 2022 20:00:10 +0000	[thread overview]
Message-ID: <164452321087.17968.3479215280295580829.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220210150451.416845-1-colin.foster@in-advantage.com>

Hello:

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

On Thu, 10 Feb 2022 07:04:50 -0800 you wrote:
> Originally submitted to net-next as part of
> 20220210041345.321216-6-colin.foster@in-advantage.com, this patch
> resolves a bug where a mutex was not guarding a buffer read that could
> be concurrently written into.
> 
> Break this out as a separate patch to be applied to net.
> 
> [...]

Here is the summary with links:
  - [v1,net,1/1] net: mscc: ocelot: fix mutex lock error during ethtool stats read
    https://git.kernel.org/netdev/net/c/7fbf6795d127

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



      parent reply	other threads:[~2022-02-10 20:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-10 15:04 Colin Foster
2022-02-10 15:04 ` [PATCH v1 net 1/1] net: mscc: ocelot: fix mutex lock error during ethtool stats read Colin Foster
2022-02-10 20: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=164452321087.17968.3479215280295580829.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=andrew@lunn.ch \
    --cc=claudiu.manoil@nxp.com \
    --cc=colin.foster@in-advantage.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=vladimir.oltean@nxp.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®