From: patchwork-bot+netdevbpf@kernel.org
To: David Howells <dhowells@redhat.com>
Cc: netdev@vger.kernel.org, ayush.sawal@chelsio.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, willemdebruijn.kernel@gmail.com,
dsahern@kernel.org, willy@infradead.org, axboe@kernel.dk,
simon.horman@corigine.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/2] splice, net: Handle MSG_SPLICE_PAGES in Chelsio-TLS
Date: Thu, 01 Jun 2023 12:00:20 +0000 [thread overview]
Message-ID: <168562082029.29159.8707546224300597535.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230531110008.642903-1-dhowells@redhat.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Wed, 31 May 2023 12:00:06 +0100 you wrote:
> Here are patches to make Chelsio-TLS handle the MSG_SPLICE_PAGES internal
> sendmsg flag. MSG_SPLICE_PAGES is an internal hint that tells the protocol
> that it should splice the pages supplied if it can. Its sendpage
> implementation is then turned into a wrapper around that.
>
> I've pushed the patches here also:
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] chelsio: Support MSG_SPLICE_PAGES
https://git.kernel.org/netdev/net-next/c/116f7b361ebb
- [net-next,v2,2/2] chelsio: Convert chtls_sendpage() to use MSG_SPLICE_PAGES
https://git.kernel.org/netdev/net-next/c/26acc982c1c5
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:[~2023-06-01 12:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 11:00 [PATCH net-next v2 0/2] splice, net: Handle MSG_SPLICE_PAGES in Chelsio-TLS David Howells
2023-05-31 11:00 ` [PATCH net-next v2 1/2] chelsio: Support MSG_SPLICE_PAGES David Howells
2023-05-31 11:00 ` [PATCH net-next v2 2/2] chelsio: Convert chtls_sendpage() to use MSG_SPLICE_PAGES David Howells
2023-06-01 12: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=168562082029.29159.8707546224300597535.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=axboe@kernel.dk \
--cc=ayush.sawal@chelsio.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=simon.horman@corigine.com \
--cc=willemdebruijn.kernel@gmail.com \
--cc=willy@infradead.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