ntb.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Eric Pilmore (GigaIO) <epilmore@gigaio.com>
Cc: netdev@vger.kernel.org, dmaengine@vger.kernel.org,
	linux-kernel@vger.kernel.org, ntb@lists.linux.dev,
	allenbh@gmail.com, dave.jiang@intel.com, jdmason@kudzu.us
Subject: Re: [PATCH v2] ntb_netdev: Use dev_kfree_skb_any() in interrupt context
Date: Mon, 12 Dec 2022 21:00:16 +0000	[thread overview]
Message-ID: <167087881634.21711.12961648575460625809.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221209000659.8318-1-epilmore@gigaio.com>

Hello:

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

On Thu,  8 Dec 2022 16:06:59 -0800 you wrote:
> From: Eric Pilmore <epilmore@gigaio.com>
> 
> TX/RX callback handlers (ntb_netdev_tx_handler(),
> ntb_netdev_rx_handler()) can be called in interrupt
> context via the DMA framework when the respective
> DMA operations have completed. As such, any calls
> by these routines to free skb's, should use the
> interrupt context safe dev_kfree_skb_any() function.
> 
> [...]

Here is the summary with links:
  - [v2] ntb_netdev: Use dev_kfree_skb_any() in interrupt context
    https://git.kernel.org/netdev/net/c/5f7d78b2b12a

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-12-12 21:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-09  0:06 [PATCH v2] ntb_netdev: Use dev_kfree_skb_any() in interrupt context epilmore
2022-12-09  0:20 ` Dave Jiang
2022-12-12 21: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=167087881634.21711.12961648575460625809.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=allenbh@gmail.com \
    --cc=dave.jiang@intel.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=epilmore@gigaio.com \
    --cc=jdmason@kudzu.us \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=ntb@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).