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,v3 0/6] ravb: Align Rx descriptor setup and maintenance
Date: Wed, 06 Mar 2024 11:30:34 +0000 [thread overview]
Message-ID: <170972463446.20219.15728780718001738211.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240304110858.117100-1-niklas.soderlund+renesas@ragnatech.se>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Mon, 4 Mar 2024 12:08:52 +0100 you wrote:
> Hello,
>
> When RZ/G2L support was added the Rx code path was split in two, one to
> support R-Car and one to support RZ/G2L. One reason for this is that
> R-Car uses the extended Rx descriptor format, while RZ/G2L uses the
> normal descriptor format.
>
> [...]
Here is the summary with links:
- [net-next,v3,1/6] ravb: Group descriptor types used in Rx ring
https://git.kernel.org/netdev/net-next/c/4123c3fbf863
- [net-next,v3,2/6] ravb: Make it clear the information relates to maximum frame size
https://git.kernel.org/netdev/net-next/c/e82700b8662c
- [net-next,v3,3/6] ravb: Create helper to allocate skb and align it
https://git.kernel.org/netdev/net-next/c/cfbad64706c1
- [net-next,v3,4/6] ravb: Use the max frame size from hardware info for RZ/G2L
https://git.kernel.org/netdev/net-next/c/496863388136
- [net-next,v3,5/6] ravb: Move maximum Rx descriptor data usage to info struct
https://git.kernel.org/netdev/net-next/c/555419b2259b
- [net-next,v3,6/6] ravb: Unify Rx ring maintenance code paths
https://git.kernel.org/netdev/net-next/c/644d037b2c44
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-06 11:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 11:08 [net-next,v3 0/6] ravb: Align Rx descriptor setup and maintenance Niklas Söderlund
2024-03-04 11:08 ` [net-next,v3 1/6] ravb: Group descriptor types used in Rx ring Niklas Söderlund
2024-03-04 11:08 ` [net-next,v3 2/6] ravb: Make it clear the information relates to maximum frame size Niklas Söderlund
2024-03-04 11:08 ` [net-next,v3 3/6] ravb: Create helper to allocate skb and align it Niklas Söderlund
2024-03-04 11:08 ` [net-next,v3 4/6] ravb: Use the max frame size from hardware info for RZ/G2L Niklas Söderlund
2024-03-04 11:08 ` [net-next,v3 5/6] ravb: Move maximum Rx descriptor data usage to info struct Niklas Söderlund
2024-03-04 11:08 ` [net-next,v3 6/6] ravb: Unify Rx ring maintenance code paths Niklas Söderlund
2024-03-06 11: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=170972463446.20219.15728780718001738211.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).