[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZXqlWT2JYg0sa7IF@infradead.org>
Date: Wed, 13 Dec 2023 22:48:57 -0800
From: Christoph Hellwig <hch@...radead.org>
To: patchwork-bot+netdevbpf@...nel.org
Cc: Mina Almasry <almasrymina@...gle.com>, shailend@...gle.com,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-doc@...r.kernel.org, linux-arch@...r.kernel.org,
linux-kselftest@...r.kernel.org, bpf@...r.kernel.org,
linux-media@...r.kernel.org, dri-devel@...ts.freedesktop.org,
davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
pabeni@...hat.com, corbet@....net, jeroendb@...gle.com,
pkaligineedi@...gle.com, hawk@...nel.org,
ilias.apalodimas@...aro.org, arnd@...db.de, dsahern@...nel.org,
willemdebruijn.kernel@...il.com, shuah@...nel.org,
sumit.semwal@...aro.org, christian.koenig@....com,
linyunsheng@...wei.com, hramamurthy@...gle.com, shakeelb@...gle.com
Subject: Re: [net-next v1 00/16] Device Memory TCP
On Thu, Dec 14, 2023 at 06:20:27AM +0000, patchwork-bot+netdevbpf@...nel.org wrote:
> Hello:
>
> This series was applied to netdev/net-next.git (main)
> by Jakub Kicinski <kuba@...nel.org>:
Umm, this is still very broken in intraction with other subsystems.
Please don't push ahead so quickly.
Powered by blists - more mailing lists