From: Yunsheng Lin <linyunsheng@huawei.com>
To: <davem@davemloft.net>, <kuba@kernel.org>, <pabeni@redhat.com>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Jesper Dangaard Brouer <hawk@kernel.org>,
John Fastabend <john.fastabend@gmail.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>, <bpf@vger.kernel.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
Jason Wang <jasowang@redhat.com>
Subject: Re: [PATCH net-next v3 0/5] remove page frag implementation in vhost_net
Date: Mon, 29 Jan 2024 20:40:37 +0800 [thread overview]
Message-ID: <65eb8581-5cd8-8759-d598-c6711608b0c7@huawei.com> (raw)
In-Reply-To: <20240123104250.9103-1-linyunsheng@huawei.com>
+cc Micheal and Jason
On 2024/1/23 18:42, Yunsheng Lin wrote:
Hi, Micheal and Jason
Is this patchset supposed to go through vhost tree instead of net-next?
As the state is changed to 'Not applicable' in the netdevbpf patchwork,
according to maintainer-netdev.rst:
Not applicable patch is expected to be applied outside of the networking
subsystem
>
next prev parent reply other threads:[~2024-01-29 12:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-23 10:42 Yunsheng Lin
2024-01-23 10:42 ` [PATCH net-next v3 1/5] mm/page_alloc: modify page_frag_alloc_align() to accept align as an argument Yunsheng Lin
2024-01-23 10:42 ` [PATCH net-next v3 2/5] page_frag: unify gfp bits for order 3 page allocation Yunsheng Lin
2024-01-23 10:42 ` [PATCH net-next v3 3/5] net: introduce page_frag_cache_drain() Yunsheng Lin
2024-01-23 10:42 ` [PATCH net-next v3 4/5] vhost/net: remove vhost_net_page_frag_refill() Yunsheng Lin
2024-01-23 10:42 ` [PATCH net-next v3 5/5] tools: virtio: introduce vhost_net_test Yunsheng Lin
2024-01-29 12:40 ` Yunsheng Lin [this message]
2024-01-30 2:08 ` [PATCH net-next v3 0/5] remove page frag implementation in vhost_net Jakub Kicinski
2024-01-30 10:38 ` Yunsheng Lin
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=65eb8581-5cd8-8759-d598-c6711608b0c7@huawei.com \
--to=linyunsheng@huawei.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=hawk@kernel.org \
--cc=jasowang@redhat.com \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®