All of lore.kernel.org
 help / color / mirror / Atom feed
From: Halil Pasic <pasic@linux.ibm.com>
To: Parav Pandit <parav@nvidia.com>
Cc: "mst@redhat.com" <mst@redhat.com>,
	"virtio-dev@lists.oasis-open.org"
	<virtio-dev@lists.oasis-open.org>,
	"virtio-comment@lists.oasis-open.org"
	<virtio-comment@lists.oasis-open.org>,
	"si-wei.liu@oracle.com" <si-wei.liu@oracle.com>,
	Halil Pasic <pasic@linux.ibm.com>
Subject: [virtio-comment] Re: [virtio-dev] [PATCH v9] virtio-network: Clarify VLAN filter table configuration
Date: Mon, 23 Jan 2023 15:49:47 +0100	[thread overview]
Message-ID: <20230123154947.35f1f52a.pasic@linux.ibm.com> (raw)
In-Reply-To: <PH0PR12MB54814E64310DE64E19ABD7DADCC89@PH0PR12MB5481.namprd12.prod.outlook.com>

On Mon, 23 Jan 2023 12:41:16 +0000
Parav Pandit <parav@nvidia.com> wrote:

> > From: Halil Pasic <pasic@linux.ibm.com>
> > Sent: Monday, January 23, 2023 6:40 AM
> > 
> > On Wed, 11 Jan 2023 01:09:45 +0200
> > Parav Pandit <parav@nvidia.com> wrote:
> >   
> > > The filtering behavior of the VLAN filter commands is not very clear
> > > as discussed in thread [1].  
> >   
> > >
> > > Hence, add the command description and device requirements for it.
> > >
> > > [1]
> > > https://lists.oasis-open.org/archives/virtio-dev/202301/msg00136.html  
> > 
> > Sorry I could not find the discussion. Can you point me to the email where the
> > discussion starts?
> >  
> Latest patch is for this change is : https://lists.oasis-open.org/archives/virtio-dev/202301/msg00231.html
> 

Sorry, my bad. Should I repost my feedback on v10 or should we continue
here? AFAICT v10 is a rebase on the directory structure stuff, so the
text should be the same.

> There was past discussion at https://www.mail-archive.com/qemu-devel@nongnu.org/msg913433.html

That is a completely different discussion than provided under [1] in the
commit message. Right? So the link provided is just wrong?

Regards,
Halil

This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.

In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.

Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/


  reply	other threads:[~2023-01-23 14:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-10 23:09 [virtio-dev] [PATCH v9] virtio-network: Clarify VLAN filter table configuration Parav Pandit
2023-01-23 11:40 ` [virtio-comment] " Halil Pasic
2023-01-23 12:41   ` [virtio-comment] " Parav Pandit
2023-01-23 14:49     ` Halil Pasic [this message]
2023-01-23 14:54       ` Parav Pandit

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=20230123154947.35f1f52a.pasic@linux.ibm.com \
    --to=pasic@linux.ibm.com \
    --cc=mst@redhat.com \
    --cc=parav@nvidia.com \
    --cc=si-wei.liu@oracle.com \
    --cc=virtio-comment@lists.oasis-open.org \
    --cc=virtio-dev@lists.oasis-open.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 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.