All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Albert Esteve <aesteve@redhat.com>
Cc: virtio-dev@lists.linux.dev, Matti.Moell@opensynergy.com,
	cohuck@redhat.com, acourbot@chromium.org,
	daniel.almeida@collabora.com, Alexander.Gordeev@opensynergy.com,
	changyeon@google.com, alex.bennee@linaro.org,
	gurchetansingh@google.com, ribalda@google.com,
	nicolas.dufresne@collabora.com, eballetb@redhat.com,
	linux-media@vger.kernel.org, virtio-comment@lists.oasis-open.org
Subject: Re: [PATCH v2 0/1] virtio-media: Add device specification
Date: Fri, 7 Jun 2024 06:22:16 -0400	[thread overview]
Message-ID: <20240607062139-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CADSE00KP+dsN5W0DHzML8f4wjiH-NQEifQ5zxLusw65mEUb+wA@mail.gmail.com>

On Fri, Jun 07, 2024 at 11:48:36AM +0200, Albert Esteve wrote:
> 
> 
> On Fri, Jun 7, 2024 at 11:41 AM Michael S. Tsirkin <mst@redhat.com> wrote:
> 
>     On Fri, Jun 07, 2024 at 10:00:44AM +0200, Albert Esteve wrote:
>     > Hi,
>     >
>     > This a formal attempt of including virtio-media
>     > device specification.
> 
>     This was sent to a wrong mailing list.
>     Please repost to the correct list.
> 
>     Albert, when you subscribed to virtio-dev you should
>     have received a message that read, in part:
> 
>     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).
> 
>     To do:
>     - send email preferably in text format (best for archiving)
> 
>     Not to do:
>     - copy both virtio-dev and virtio-comment mailing lists (instead, pick
>       one)
>     - send full copies of the virtio spec (in any format)
> 
> 
> 
>     So what made you send a specification change proposal to
>     virtio-dev, and also copy the defunct, non-functional
>     list at virtio-dev@lists.oasis-open.org ?
> 
> 
>     Was the message unclear? If yes I'd like to improve it.
> 
> 
> My bad.
> The instructions were clear, and I set up the mail to be sent to the
> correct virtio-dev mailing list address.


Hmm no, it's actually virtio-comment@lists.linux.dev for change
proposals for the Virtio specification which is what you have here.


> But I had the configuration
> of the project set to automatically add both of the old addresses to the
> patch. I only noticed after sending, so the damage was already
> made. 
> 
> I will fix it for the next drop.
>  
> 
> 
> 
>     --
>     MST
> 
> 


  reply	other threads:[~2024-06-07 10:22 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-07  8:00 [PATCH v2 0/1] virtio-media: Add device specification Albert Esteve
2024-06-07  8:00 ` [PATCH v2 1/1] virtio-media: Add virtio media " Albert Esteve
2024-06-07  8:43   ` Hans Verkuil
2024-06-08  1:24     ` Alexandre Courbot
2024-06-20 12:45       ` Hans Verkuil
2024-06-20 12:53         ` Alexandre Courbot
2024-06-20 13:33           ` Hans Verkuil
2024-06-07  8:21 ` [PATCH v2 0/1] virtio-media: Add " Albert Esteve
2024-06-07  9:41 ` Michael S. Tsirkin
2024-06-07  9:48   ` Albert Esteve
2024-06-07 10:22     ` Michael S. Tsirkin [this message]
2024-06-07 10:54       ` Albert Esteve
2024-06-07 13:28 ` Alexander Gordeev
2024-06-08  1:50   ` Alexandre Courbot
  -- strict thread matches above, loose matches on Subject: below --
2024-06-07 13:35 Albert Esteve
2024-06-10  9:09 ` Albert Esteve
2024-06-10  9:24   ` Albert Esteve
2024-06-11 10:10     ` Alexander Gordeev
2024-06-11 12:24       ` Albert Esteve
2024-06-15  8:31         ` Alexander Gordeev
2024-06-11 12:12   ` Alexander Gordeev

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=20240607062139-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=Alexander.Gordeev@opensynergy.com \
    --cc=Matti.Moell@opensynergy.com \
    --cc=acourbot@chromium.org \
    --cc=aesteve@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=changyeon@google.com \
    --cc=cohuck@redhat.com \
    --cc=daniel.almeida@collabora.com \
    --cc=eballetb@redhat.com \
    --cc=gurchetansingh@google.com \
    --cc=linux-media@vger.kernel.org \
    --cc=nicolas.dufresne@collabora.com \
    --cc=ribalda@google.com \
    --cc=virtio-comment@lists.oasis-open.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.