All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: <alejandro.lucero-palau@amd.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	linux-net-drivers@amd.com, netdev@vger.kernel.org,
	ecree.xilinx@gmail.com, habetsm.xilinx@gmail.com,
	edumazet@google.com, fw@strlen.de
Subject: Re: [PATCH v3 net] sfc: disable softirqs for ptp TX
Date: Thu, 28 Jul 2022 01:30:13 +0000	[thread overview]
Message-ID: <165897181313.2015.11008674774502875788.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220726064504.49613-1-alejandro.lucero-palau@amd.com>

Hello:

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

On Tue, 26 Jul 2022 08:45:04 +0200 you wrote:
> From: Alejandro Lucero <alejandro.lucero-palau@amd.com>
> 
> Sending a PTP packet can imply to use the normal TX driver datapath but
> invoked from the driver's ptp worker. The kernel generic TX code
> disables softirqs and preemption before calling specific driver TX code,
> but the ptp worker does not. Although current ptp driver functionality
> does not require it, there are several reasons for doing so:
> 
> [...]

Here is the summary with links:
  - [v3,net] sfc: disable softirqs for ptp TX
    https://git.kernel.org/netdev/net/c/67c3b611d92f

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-07-28  1:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-26  6:45 [PATCH v3 net] sfc: disable softirqs for ptp TX alejandro.lucero-palau
2022-07-27  3:56 ` Taehee Yoo
2022-07-28  1:30 ` 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=165897181313.2015.11008674774502875788.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alejandro.lucero-palau@amd.com \
    --cc=davem@davemloft.net \
    --cc=ecree.xilinx@gmail.com \
    --cc=edumazet@google.com \
    --cc=fw@strlen.de \
    --cc=habetsm.xilinx@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-net-drivers@amd.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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.