From: patchwork-bot+netdevbpf@kernel.org
To: Mina Almasry <almasrymina@google.com>
Cc: netdev@vger.kernel.org, kuba@kernel.org, edumazet@google.com,
willemb@google.com, davem@davemloft.net,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
pabeni@redhat.com, horms@kernel.org, corbet@lwn.net,
yi1.lai@linux.intel.com, sdf@fomichev.me
Subject: Re: [PATCH net v2 1/2] net: fix SO_DEVMEM_DONTNEED looping too long
Date: Tue, 12 Nov 2024 02:40:29 +0000 [thread overview]
Message-ID: <173137922901.57225.8157709932343230683.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241107210331.3044434-1-almasrymina@google.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 7 Nov 2024 21:03:30 +0000 you wrote:
> Exit early if we're freeing more than 1024 frags, to prevent
> looping too long.
>
> Also minor code cleanups:
> - Flip checks to reduce indentation.
> - Use sizeof(*tokens) everywhere for consistentcy.
>
> [...]
Here is the summary with links:
- [net,v2,1/2] net: fix SO_DEVMEM_DONTNEED looping too long
https://git.kernel.org/netdev/net/c/f2685c00c322
- [net,v2,2/2] net: clarify SO_DEVMEM_DONTNEED behavior in documentation
https://git.kernel.org/netdev/net/c/102d1404c385
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-11-12 2:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 21:03 [PATCH net v2 1/2] net: fix SO_DEVMEM_DONTNEED looping too long Mina Almasry
2024-11-07 21:03 ` [PATCH net v2 2/2] net: clarify SO_DEVMEM_DONTNEED behavior in documentation Mina Almasry
2024-11-08 1:30 ` Stanislav Fomichev
2024-11-08 1:40 ` Mina Almasry
2024-11-08 3:01 ` Stanislav Fomichev
2024-11-08 16:30 ` Mina Almasry
2024-11-08 18:07 ` Stanislav Fomichev
2024-11-08 18:45 ` Mina Almasry
2024-11-08 1:28 ` [PATCH net v2 1/2] net: fix SO_DEVMEM_DONTNEED looping too long Stanislav Fomichev
2024-11-08 1:33 ` Mina Almasry
2024-11-08 2:58 ` Stanislav Fomichev
2024-11-12 2:40 ` 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=173137922901.57225.8157709932343230683.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=almasrymina@google.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--cc=willemb@google.com \
--cc=yi1.lai@linux.intel.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.