mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: 'Horatiu Vultur' <horatiu.vultur@microchip.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, UNGLinuxDriver@microchip.com
Subject: Re: [PATCH net] net: lan966x: Fix unmapping of received frames using FDMA
Date: Wed, 02 Nov 2022 04:30:17 +0000	[thread overview]
Message-ID: <166736341750.16570.4089002649799561843.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221031133421.1283196-1-horatiu.vultur@microchip.com>

Hello:

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

On Mon, 31 Oct 2022 14:34:21 +0100 you wrote:
> When lan966x was receiving a frame, then it was building the skb and
> after that it was calling dma_unmap_single with frame size as the
> length. This actually has 2 issues:
> 1. It is using a length to map and a different length to unmap.
> 2. When the unmap was happening, the data was sync for cpu but it could
>    be that this will overwrite what build_skb was initializing.
> 
> [...]

Here is the summary with links:
  - [net] net: lan966x: Fix unmapping of received frames using FDMA
    https://git.kernel.org/netdev/net/c/fc57062f98b0

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



      reply	other threads:[~2022-11-02  4:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-31 13:34 Horatiu Vultur
2022-11-02  4: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=166736341750.16570.4089002649799561843.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horatiu.vultur@microchip.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome