From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?q?Niklas_S=C3=B6derlund_=3Cniklas=2Esoderlund+renesas=40ragnatech=2E?=@ci.codeaurora.org,
=?utf-8?q?se=3E?=@ci.codeaurora.org
Cc: s.shtylyov@omp.ru, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, biju.das.jz@bp.renesas.com,
claudiu.beznea.uj@bp.renesas.com,
yoshihiro.shimoda.uh@renesas.com, netdev@vger.kernel.org,
linux-renesas-soc@vger.kernel.org
Subject: Re: [net-next] ravb: Correct buffer size to map for R-Car Rx
Date: Mon, 11 Mar 2024 22:50:37 +0000 [thread overview]
Message-ID: <171019743700.8733.13687567059309127067.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240308224237.496924-1-niklas.soderlund+renesas@ragnatech.se>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 8 Mar 2024 23:42:37 +0100 you wrote:
> When creating a helper to allocate and align an skb one location where
> the skb data size was updated was missed. This can lead to a warning
> being printed when the memory is being unmapped as it now always unmap
> the maximum frame size, instead of the size after it have been
> aligned.
>
> This was correctly done for RZ/G2L but missed for R-Car.
>
> [...]
Here is the summary with links:
- [net-next] ravb: Correct buffer size to map for R-Car Rx
https://git.kernel.org/netdev/net-next/c/a290d4cb892d
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-03-11 22:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-08 22:42 [net-next] ravb: Correct buffer size to map for R-Car Rx Niklas Söderlund
2024-03-09 19:32 ` Sergey Shtylyov
2024-03-11 9:24 ` Simon Horman
2024-03-11 9:39 ` Geert Uytterhoeven
2024-03-11 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=171019743700.8733.13687567059309127067.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?q?Niklas_S=C3=B6derlund_=3Cniklas=2Esoderlund+renesas=40ragnatech=2E?=@ci.codeaurora.org \
--cc==?utf-8?q?se=3E?=@ci.codeaurora.org \
--cc=biju.das.jz@bp.renesas.com \
--cc=claudiu.beznea.uj@bp.renesas.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=s.shtylyov@omp.ru \
--cc=yoshihiro.shimoda.uh@renesas.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).