From: patchwork-bot+netdevbpf@kernel.org
To: Suraj Gupta <suraj.gupta2@amd.com>
Cc: radhey.shyam.pandey@amd.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, michal.simek@amd.com, netdev@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, git@amd.com,
harini.katakam@amd.com
Subject: Re: [PATCH net 0/2] net: xilinx: axienet: Fix kernel crash in dmaengine transmit path
Date: Sun, 03 Nov 2024 22:50:28 +0000 [thread overview]
Message-ID: <173067422875.3271988.4124250768668395576.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241030062533.2527042-1-suraj.gupta2@amd.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 30 Oct 2024 11:55:31 +0530 you wrote:
> This series fixes kernel crash in dmaengine transmit path. To fix it,
> enqueue Tx packets in dql before starting dmaengine and check if queue is
> not stopped.
>
> Suraj Gupta (2):
> net: xilinx: axienet: Enqueue Tx packets in dql before dmaengine
> starts
> net: xilinx: axienet: Check if Tx queue enabled
>
> [...]
Here is the summary with links:
- [net,1/2] net: xilinx: axienet: Enqueue Tx packets in dql before dmaengine starts
https://git.kernel.org/netdev/net/c/5ccdcdf186ae
- [net,2/2] net: xilinx: axienet: Check if Tx queue enabled
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-11-03 22:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-30 6:25 [PATCH net 0/2] net: xilinx: axienet: Fix kernel crash in dmaengine transmit path Suraj Gupta
2024-10-30 6:25 ` [PATCH net 1/2] net: xilinx: axienet: Enqueue Tx packets in dql before dmaengine starts Suraj Gupta
2024-10-30 6:25 ` [PATCH net 2/2] net: xilinx: axienet: Check if Tx queue enabled Suraj Gupta
2024-11-03 22:37 ` Jakub Kicinski
2024-11-04 7:08 ` Gupta, Suraj
2024-11-03 22:50 ` 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=173067422875.3271988.4124250768668395576.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=git@amd.com \
--cc=harini.katakam@amd.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@amd.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=radhey.shyam.pandey@amd.com \
--cc=suraj.gupta2@amd.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;
as well as URLs for NNTP newsgroup(s).