Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Mon, 5 Dec 2022 17:37:35 -0800
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
Message-ID: <20221205173735.6123b941@kernel.org>
In-Reply-To: <20221205122214.bky3oxipck4hsqqe@sgarzare-redhat>
References: <20221202173520.10428-1-bobby.eshleman@bytedance.com>
        <20221205122214.bky3oxipck4hsqqe@sgarzare-redhat>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Precedence: bulk

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.