Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Subject: Re: [RFC PATCH v3 0/6] virtio/vsock: introduce MSG_EOR flag for
 SEQPACKET
From:   Arseny Krasnov <arseny.krasnov@kaspersky.com>
To:     Stefano Garzarella <sgarzare@redhat.com>
CC:     Stefan Hajnoczi <stefanha@redhat.com>,
        "Michael S. Tsirkin" <mst@redhat.com>,
        Jason Wang <jasowang@redhat.com>,
        "David S. Miller" <davem@davemloft.net>,
        Jakub Kicinski <kuba@kernel.org>,
        Norbert Slusarek <nslusarek@gmx.net>,
        Andra Paraschiv <andraprs@amazon.com>,
        Colin Ian King <colin.king@canonical.com>,
        "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
        "virtualization@lists.linux-foundation.org" 
        <virtualization@lists.linux-foundation.org>,
        "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        "stsp2@yandex.ru" <stsp2@yandex.ru>,
        "oxffffaa@gmail.com" <oxffffaa@gmail.com>
References: <20210816085036.4173627-1-arseny.krasnov@kaspersky.com>
 <3f3fc268-10fc-1917-32c2-dc0e7737dc48@kaspersky.com>
 <20210824100523.yn5hgiycz2ysdnvm@steredhat>
 <d28ff03e-c8ab-f7c6-68a2-90c9a400d029@kaspersky.com>
 <20210824103137.v3fny2yc5ww46p33@steredhat>
 <0c0a7b61-524e-ab44-7d7e-b35bd094c7ca@kaspersky.com>
Message-ID: <f251d84e-558e-9618-403c-253a1c2a1ea3@kaspersky.com>
Date:   Mon, 30 Aug 2021 08:26:12 +0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <0c0a7b61-524e-ab44-7d7e-b35bd094c7ca@kaspersky.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
Content-Language: en-US
X-KSE-AttachmentFiltering-Interceptor-Info: no applicable attachment filtering
 rules found
X-KSE-Antivirus-Interceptor-Info: scan successful
X-KSE-Antivirus-Info: Clean, bases: 30.08.2021 3:54:00
X-KSE-BulkMessagesFiltering-Scan-Result: InTheLimit
X-KSE-AttachmentFiltering-Interceptor-Info: no applicable attachment filtering
 rules found
X-KSE-BulkMessagesFiltering-Scan-Result: InTheLimit
X-KLMS-Rule-ID: 52
X-KLMS-Message-Action: clean
X-KLMS-AntiSpam-Status: not scanned, disabled by settings
X-KLMS-AntiSpam-Interceptor-Info: not scanned
X-KLMS-AntiPhishing: Clean, bases: 2021/08/30 03:39:00
X-KLMS-AntiVirus: Kaspersky Security for Linux Mail Server, version 8.0.3.30, bases: 2021/08/30 03:40:00 #17126216
X-KLMS-AntiVirus-Status: Clean, skipped
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org


On 24.08.2021 14:35, Arseny Krasnov wrote:
> On 24.08.2021 13:31, Stefano Garzarella wrote:
>> Caution: This is an external email. Be cautious while opening links or attachments.
>>
>>
>>
>> On Tue, Aug 24, 2021 at 01:18:06PM +0300, Arseny Krasnov wrote:
>>> On 24.08.2021 13:05, Stefano Garzarella wrote:
>>>> Caution: This is an external email. Be cautious while opening links or attachments.
>>>>
>>>>
>>>>
>>>> Hi Arseny,
>>>>
>>>> On Mon, Aug 23, 2021 at 09:41:16PM +0300, Arseny Krasnov wrote:
>>>>> Hello, please ping :)
>>>>>
>>>> Sorry, I was off last week.
>>>> I left some minor comments in the patches.
>>>>
>>>> Let's wait a bit for other comments before next version, also on the
>>>> spec, then I think you can send the next version without RFC tag.
>>>> The target should be the net-next tree, since this is a new feature.
>>> Hello,
>>>
>>> E.g. next version will be [net-next] instead of [RFC] for both
>>> kernel and spec patches?
>> Nope, net-next tag is useful only for kernel patches (net tree -
>> Documentation/networking/netdev-FAQ.rst).
> Ack

Hello,

as there are no new comments on this week, i can send

new patchsets for both kernel and spec today. Kernel patches

will be with 'net-next' tag instead of RFC, spec patches will be

without RFC tag.


Thank You

>> Thanks,
>> Stefano
>>
>>