From: patchwork-bot+netdevbpf@kernel.org
To: Nelson@ci.codeaurora.org, Shannon <shannon.nelson@amd.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
edumazet@google.com, pabeni@redhat.com, horms@kernel.org,
brett.creeley@amd.com, drivers@pensando.io
Subject: Re: [PATCH net-next v2 0/7] ionic: updates for v6.11
Date: Fri, 31 May 2024 01:30:32 +0000 [thread overview]
Message-ID: <171711903291.12927.4247643339908614644.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240529000259.25775-1-shannon.nelson@amd.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 28 May 2024 17:02:52 -0700 you wrote:
> These are a few minor fixes for the ionic driver to clean
> up a some little things that have been waiting for attention.
> These were originally sent for net, but now respun for net-next.
>
> v1: https://lore.kernel.org/netdev/20240521013715.12098-1-shannon.nelson@amd.com/
>
> Brett Creeley (3):
> ionic: Pass ionic_txq_desc to ionic_tx_tso_post
> ionic: Mark error paths in the data path as unlikely
> ionic: Use netdev_name() function instead of netdev->name
>
> [...]
Here is the summary with links:
- [net-next,v2,1/7] ionic: fix potential irq name truncation
https://git.kernel.org/netdev/net-next/c/3eb76e71b16e
- [net-next,v2,2/7] ionic: Reset LIF device while restarting LIF
https://git.kernel.org/netdev/net-next/c/8097a2f3d21a
- [net-next,v2,3/7] ionic: Pass ionic_txq_desc to ionic_tx_tso_post
https://git.kernel.org/netdev/net-next/c/4dde9588c54d
- [net-next,v2,4/7] ionic: Mark error paths in the data path as unlikely
https://git.kernel.org/netdev/net-next/c/d9c04209990b
- [net-next,v2,5/7] ionic: Use netdev_name() function instead of netdev->name
https://git.kernel.org/netdev/net-next/c/fc53d4652448
- [net-next,v2,6/7] ionic: only sync frag_len in first buffer of xdp
https://git.kernel.org/netdev/net-next/c/488da00479d5
- [net-next,v2,7/7] ionic: fix up ionic_if.h kernel-doc issues
https://git.kernel.org/netdev/net-next/c/a54e2a36b68c
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-05-31 1:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-29 0:02 [PATCH net-next v2 0/7] ionic: updates for v6.11 Shannon Nelson
2024-05-29 0:02 ` [PATCH net-next v2 1/7] ionic: fix potential irq name truncation Shannon Nelson
2024-05-29 0:02 ` [PATCH net-next v2 2/7] ionic: Reset LIF device while restarting LIF Shannon Nelson
2024-05-29 0:02 ` [PATCH net-next v2 3/7] ionic: Pass ionic_txq_desc to ionic_tx_tso_post Shannon Nelson
2024-05-29 0:02 ` [PATCH net-next v2 4/7] ionic: Mark error paths in the data path as unlikely Shannon Nelson
2024-05-29 0:02 ` [PATCH net-next v2 5/7] ionic: Use netdev_name() function instead of netdev->name Shannon Nelson
2024-05-29 5:30 ` Kalesh Anakkur Purayil
2024-05-29 0:02 ` [PATCH net-next v2 6/7] ionic: only sync frag_len in first buffer of xdp Shannon Nelson
2024-05-29 0:02 ` [PATCH net-next v2 7/7] ionic: fix up ionic_if.h kernel-doc issues Shannon Nelson
2024-05-31 1: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=171711903291.12927.4247643339908614644.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Nelson@ci.codeaurora.org \
--cc=brett.creeley@amd.com \
--cc=davem@davemloft.net \
--cc=drivers@pensando.io \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shannon.nelson@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 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.