From: patchwork-bot+netdevbpf@kernel.org
To: Julian Wiedmann <jwi@linux.ibm.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
linux-s390@vger.kernel.org, hca@linux.ibm.com,
kgraul@linux.ibm.com
Subject: Re: [PATCH net-next 0/9] s390/qeth: updates 2021-06-11
Date: Fri, 11 Jun 2021 20:00:07 +0000 [thread overview]
Message-ID: <162344160703.3583.2800269922297994117.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210611073341.1634501-1-jwi@linux.ibm.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Fri, 11 Jun 2021 09:33:32 +0200 you wrote:
> Hi Dave & Jakub,
>
> please apply the following patch series for qeth to netdev's net-next tree.
>
> This enables TX NAPI for those devices that didn't use it previously, so
> that we can eventually rip out the qdio layer's internal interrupt
> machinery.
>
> [...]
Here is the summary with links:
- [net-next,1/9] s390/qeth: count TX completion interrupts
https://git.kernel.org/netdev/net-next/c/e872d0c1249b
- [net-next,2/9] s390/qeth: also use TX NAPI for non-IQD devices
https://git.kernel.org/netdev/net-next/c/7a4b92e8e0de
- [net-next,3/9] s390/qeth: unify the tracking of active cmds on ccw device
https://git.kernel.org/netdev/net-next/c/3518ae76f2bb
- [net-next,4/9] s390/qeth: use ethtool_sprintf()
https://git.kernel.org/netdev/net-next/c/c0a0186630fb
- [net-next,5/9] s390/qeth: consolidate completion of pending TX buffers
https://git.kernel.org/netdev/net-next/c/f875d880f049
- [net-next,6/9] s390/qeth: remove QAOB's pointer to its TX buffer
https://git.kernel.org/netdev/net-next/c/838e4cc80814
- [net-next,7/9] s390/qeth: remove TX buffer's pointer to its queue
https://git.kernel.org/netdev/net-next/c/6b7ec41e574a
- [net-next,8/9] s390/qeth: shrink TX buffer struct
https://git.kernel.org/netdev/net-next/c/bb7032ddc947
- [net-next,9/9] s390/qeth: Consider dependency on SWITCHDEV module
https://git.kernel.org/netdev/net-next/c/953fb4dc4f4a
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-06-11 20:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 7:33 [PATCH net-next 0/9] s390/qeth: updates 2021-06-11 Julian Wiedmann
2021-06-11 7:33 ` [PATCH net-next 1/9] s390/qeth: count TX completion interrupts Julian Wiedmann
2021-06-11 7:33 ` [PATCH net-next 2/9] s390/qeth: also use TX NAPI for non-IQD devices Julian Wiedmann
2021-06-11 7:33 ` [PATCH net-next 3/9] s390/qeth: unify the tracking of active cmds on ccw device Julian Wiedmann
2021-06-11 7:33 ` [PATCH net-next 4/9] s390/qeth: use ethtool_sprintf() Julian Wiedmann
2021-06-11 7:33 ` [PATCH net-next 5/9] s390/qeth: consolidate completion of pending TX buffers Julian Wiedmann
2021-06-11 7:33 ` [PATCH net-next 6/9] s390/qeth: remove QAOB's pointer to its TX buffer Julian Wiedmann
2021-06-11 7:33 ` [PATCH net-next 7/9] s390/qeth: remove TX buffer's pointer to its queue Julian Wiedmann
2021-06-11 7:33 ` [PATCH net-next 8/9] s390/qeth: shrink TX buffer struct Julian Wiedmann
2021-06-11 7:33 ` [PATCH net-next 9/9] s390/qeth: Consider dependency on SWITCHDEV module Julian Wiedmann
2021-06-11 20: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=162344160703.3583.2800269922297994117.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=hca@linux.ibm.com \
--cc=jwi@linux.ibm.com \
--cc=kgraul@linux.ibm.com \
--cc=kuba@kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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