public inbox for virtio-dev@lists.linux.dev
 help / color / mirror / Atom feed
From: Paolo Abeni <pabeni@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: virtio-dev@lists.linux.dev, maxime.coquelin@redhat.com,
	Eelco Chaudron <echaudro@redhat.com>,
	Jason Wang <jasowang@redhat.com>
Subject: Re: [PATCH v3] virtio-net: define UDP tunnel offload feature
Date: Tue, 21 May 2024 09:25:51 +0200	[thread overview]
Message-ID: <2dd731c45ee016fcca416d18d21882947bbf9f9d.camel@redhat.com> (raw)
In-Reply-To: <20240520225254-mutt-send-email-mst@kernel.org>

Hi,
On Mon, 2024-05-20 at 22:55 -0400, Michael S. Tsirkin wrote:
> when you subscribed to virtio-dev you should have received this:
> 
> When to use this list:
> - questions and change proposals for Virtio drivers and devices
>   implementing the specification.
> 
> When not to use this list:
> - questions and change proposals for the Virtio specification,
>   including the specification of basic functionality, transports and
>   devices (please use the virtio-comment mailing list
>   [mailto:virtio-comment@lists.linux.dev] for this).
> 
> 
> Did you receive this? 

Yes, I received it.

> If yes was this somehow unclear?  If no why are you sending a Virtio 
> specification change proposal to virtio-dev?

Given your reply I guess my interpretation was wrong. Should I reply to
Jason and Stefano feedback here, or move the discussion entirely on
virtio-comment? 

Thanks,

Paolo


  reply	other threads:[~2024-05-21  7:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-20  8:24 [PATCH v3] virtio-net: define UDP tunnel offload feature Paolo Abeni
2024-05-20 13:00 ` Stefano Garzarella
2024-05-21  2:55 ` Michael S. Tsirkin
2024-05-21  7:25   ` Paolo Abeni [this message]
2024-05-21  7:41     ` Michael S. Tsirkin
2024-05-21 12:00       ` Paolo Abeni

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=2dd731c45ee016fcca416d18d21882947bbf9f9d.camel@redhat.com \
    --to=pabeni@redhat.com \
    --cc=echaudro@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=mst@redhat.com \
    --cc=virtio-dev@lists.linux.dev \
    /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