From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?b?Q2zDqW1lbnQgTMOpZ2VyIDxjbGVtZW50LmxlZ2VyQGJvb3RsaW4uY29tPg==?=@ci.codeaurora.org
Cc: davem@davemloft.net, kuba@kernel.org, robh+dt@kernel.org,
vladimir.oltean@nxp.com, claudiu.manoil@nxp.com,
alexandre.belloni@bootlin.com, UNGLinuxDriver@microchip.com,
andrew@lunn.ch, f.fainelli@gmail.com, linux@armlinux.org.uk,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, thomas.petazzoni@bootlin.com,
dkirjanov@suse.de, jwi@linux.ibm.com, lkp@intel.com
Subject: Re: [PATCH net-next] net: ocelot: use dma_unmap_addr to get tx buffer dma_addr
Date: Mon, 13 Dec 2021 15:00:10 +0000 [thread overview]
Message-ID: <163940761071.26947.514912105891386246.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211213082651.443577-1-clement.leger@bootlin.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Mon, 13 Dec 2021 09:26:51 +0100 you wrote:
> dma_addr was declared using DEFINE_DMA_UNMAP_ADDR() which requires to
> use dma_unmap_addr() to access it.
>
> Reported-by: kernel test robot <lkp@intel.com>
> Fixes: 753a026cfec1 ("net: ocelot: add FDMA support")
> Signed-off-by: Clément Léger <clement.leger@bootlin.com>
>
> [...]
Here is the summary with links:
- [net-next] net: ocelot: use dma_unmap_addr to get tx buffer dma_addr
https://git.kernel.org/netdev/net-next/c/3cfcda2aee94
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:[~2021-12-13 15:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-13 8:26 [PATCH net-next] net: ocelot: use dma_unmap_addr to get tx buffer dma_addr Clément Léger
2021-12-13 15: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=163940761071.26947.514912105891386246.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?b?Q2zDqW1lbnQgTMOpZ2VyIDxjbGVtZW50LmxlZ2VyQGJvb3RsaW4uY29tPg==?=@ci.codeaurora.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andrew@lunn.ch \
--cc=claudiu.manoil@nxp.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=dkirjanov@suse.de \
--cc=f.fainelli@gmail.com \
--cc=jwi@linux.ibm.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lkp@intel.com \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=thomas.petazzoni@bootlin.com \
--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 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.