From: Jakub Kicinski <kuba@kernel.org>
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: Bobby Eshleman <bobby.eshleman@bytedance.com>,
Bobby Eshleman <bobbyeshleman@gmail.com>,
Cong Wang <cong.wang@bytedance.com>,
Jiang Wang <jiang.wang@bytedance.com>,
Krasnov Arseniy <oxffffaa@gmail.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Jason Wang <jasowang@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
kvm@vger.kernel.org, virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5] virtio/vsock: replace virtio_vsock_pkt with sk_buff
Date: Mon, 5 Dec 2022 17:37:35 -0800 [thread overview]
Message-ID: <20221205173735.6123b941@kernel.org> (raw)
In-Reply-To: <20221205122214.bky3oxipck4hsqqe@sgarzare-redhat>
On Mon, 5 Dec 2022 13:22:14 +0100 Stefano Garzarella wrote:
> As pointed out in v4, this is net-next material, so you should use the
> net-next tag and base the patch on the net-next tree:
> https://www.kernel.org/doc/html/v6.0/process/maintainer-netdev.html#netdev-faq
Thanks, yes, please try to do that, makes it much less likely that
the patch will be mishandled or lost.
> I locally applied the patch on net-next and everything is fine, so maybe
> the maintainers can apply it, otherwise you should resend it with the
> right tag.
FWIW looks like all the automated guessing kicked in correctly here,
so no need to repost just for the subject tag (this time).
> Ah, in that case I suggest you send it before the next merge window
> opens (I guess next week), because net-next closes and you'll have to
> wait for the next cycle.
+1, we'll try to take a closer look & apply tomorrow unless someone
speaks up.
next prev parent reply other threads:[~2022-12-06 1:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 17:35 [PATCH v5] virtio/vsock: replace virtio_vsock_pkt with sk_buff Bobby Eshleman
2022-12-05 12:22 ` Stefano Garzarella
2022-12-06 1:37 ` Jakub Kicinski [this message]
2022-11-21 11:02 ` Bobby Eshleman
2022-12-06 10:20 ` Paolo Abeni
2022-11-21 12:01 ` Bobby Eshleman
2022-12-07 9:33 ` Paolo Abeni
2022-11-21 20:19 ` Bobby Eshleman
2022-12-06 22:15 ` Michael S. Tsirkin
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=20221205173735.6123b941@kernel.org \
--to=kuba@kernel.org \
--cc=bobby.eshleman@bytedance.com \
--cc=bobbyeshleman@gmail.com \
--cc=cong.wang@bytedance.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jasowang@redhat.com \
--cc=jiang.wang@bytedance.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=oxffffaa@gmail.com \
--cc=pabeni@redhat.com \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.com \
--cc=virtualization@lists.linux-foundation.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).