From: Jakub Kicinski <kuba@kernel.org>
To: Mina Almasry <almasrymina@google.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Jesper Dangaard Brouer <hawk@kernel.org>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
Shuah Khan <shuah@kernel.org>
Subject: Re: [PATCH net-next v1 0/7] devmem TCP fixes
Date: Thu, 31 Oct 2024 19:41:01 -0700 [thread overview]
Message-ID: <20241031194101.301f1f72@kernel.org> (raw)
In-Reply-To: <20241029205524.1306364-1-almasrymina@google.com>
On Tue, 29 Oct 2024 20:55:20 +0000 Mina Almasry wrote:
> A few unrelated devmem TCP fixes bundled in a series for some
> convenience (if that's ok).
These two should go to net I presume? It's missing input validation.
Either way you gotta repost either as two properly separate series,
or combine them as one, cause right now they are neither and patchwork
doesn't recognize they are related.
next prev parent reply other threads:[~2024-11-01 2:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 20:55 [PATCH net-next v1 0/7] devmem TCP fixes Mina Almasry
2024-10-29 20:55 ` [PATCH net-next v1 6/7] net: fix SO_DEVMEM_DONTNEED looping too long Mina Almasry
2024-10-30 14:33 ` Stanislav Fomichev
2024-10-30 14:46 ` Mina Almasry
2024-10-30 15:06 ` Stanislav Fomichev
2024-11-05 21:28 ` Mina Almasry
2024-11-05 21:46 ` Stanislav Fomichev
2024-11-05 23:43 ` Mina Almasry
2024-11-06 0:13 ` Stanislav Fomichev
2024-10-29 20:55 ` [PATCH net-next v1 7/7] ncdevmem: add test for too many token_count Mina Almasry
2024-11-01 2:41 ` Jakub Kicinski [this message]
2024-11-01 13:14 ` [PATCH net-next v1 0/7] devmem TCP fixes Mina Almasry
2024-11-02 2:27 ` Jakub Kicinski
-- strict thread matches above, loose matches on Subject: below --
2024-10-29 20:45 Mina Almasry
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=20241031194101.301f1f72@kernel.org \
--to=kuba@kernel.org \
--cc=almasrymina@google.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=horms@kernel.org \
--cc=ilias.apalodimas@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@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;
as well as URLs for NNTP newsgroup(s).