From: Cornelia Huck <cohuck@redhat.com>
To: Parav Pandit <parav@nvidia.com>,
"mst@redhat.com" <mst@redhat.com>,
"virtio-dev@lists.oasis-open.org"
<virtio-dev@lists.oasis-open.org>
Cc: "virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>,
Shahaf Shuler <shahafs@nvidia.com>
Subject: Re: [virtio-comment] RE: [PATCH v3 0/2] virtio-net: Improve dev config layout
Date: Wed, 08 Mar 2023 11:07:48 +0100 [thread overview]
Message-ID: <87lek7lfnv.fsf@redhat.com> (raw)
In-Reply-To: <PH0PR12MB548186EADD442CF688EA21BEDCB79@PH0PR12MB5481.namprd12.prod.outlook.com>
On Tue, Mar 07 2023, Parav Pandit <parav@nvidia.com> wrote:
> Hi Cornelia,
>
>> -----Original Message-----
>> From: Cornelia Huck <cohuck@redhat.com>
>> Sent: Monday, March 6, 2023 9:32 AM
>> To: Parav Pandit <parav@nvidia.com>; mst@redhat.com; virtio-dev@lists.oasis-
>> open.org
>> Cc: virtio-comment@lists.oasis-open.org; Shahaf Shuler <shahafs@nvidia.com>
>> Subject: RE: [PATCH v3 0/2] virtio-net: Improve dev config layout
>>
>> On Tue, Feb 21 2023, Parav Pandit <parav@nvidia.com> wrote:
>>
>> >> From: Parav Pandit <parav@nvidia.com>
>> >> Sent: Friday, February 17, 2023 10:45 AM
>> >
>> >> Patch summary:
>> >> patch-1: consolidate read only field at one place in driver
>> >> requirements
>> >> patch-2: define device configuration layout before describing its fields.
>> >>
>> >> changelog:
>> >> v2->v3:
>> >> - split into two patches
>> >> - move read only description to driver requirements section
>> >
>> > These 2 patches are reviewed.
>> > Can you please open a ballot for it?
>> > Github issue:
>> > https://lists.oasis-open.org/archives/virtio-dev/202302/msg00405.html
>> > And the github description has the latest link this time. :)
>>
>> I think something went wrong here... the link above points to this series (i.e. not
>> the latest one), and so does the github issue, and therefore the ballot. I think we
>> should withdraw the ballot?
>
> Please withdraw.
>
> Right link is: [1].
> Please create the new ballot with link [1].
>
> [1] https://lists.oasis-open.org/archives/virtio-dev/202302/msg00556.html
Done.
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/
WARNING: multiple messages have this Message-ID (diff)
From: Cornelia Huck <cohuck@redhat.com>
To: Parav Pandit <parav@nvidia.com>,
"mst@redhat.com" <mst@redhat.com>,
"virtio-dev@lists.oasis-open.org"
<virtio-dev@lists.oasis-open.org>
Cc: "virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>,
Shahaf Shuler <shahafs@nvidia.com>
Subject: [virtio-dev] Re: [virtio-comment] RE: [PATCH v3 0/2] virtio-net: Improve dev config layout
Date: Wed, 08 Mar 2023 11:07:48 +0100 [thread overview]
Message-ID: <87lek7lfnv.fsf@redhat.com> (raw)
In-Reply-To: <PH0PR12MB548186EADD442CF688EA21BEDCB79@PH0PR12MB5481.namprd12.prod.outlook.com>
On Tue, Mar 07 2023, Parav Pandit <parav@nvidia.com> wrote:
> Hi Cornelia,
>
>> -----Original Message-----
>> From: Cornelia Huck <cohuck@redhat.com>
>> Sent: Monday, March 6, 2023 9:32 AM
>> To: Parav Pandit <parav@nvidia.com>; mst@redhat.com; virtio-dev@lists.oasis-
>> open.org
>> Cc: virtio-comment@lists.oasis-open.org; Shahaf Shuler <shahafs@nvidia.com>
>> Subject: RE: [PATCH v3 0/2] virtio-net: Improve dev config layout
>>
>> On Tue, Feb 21 2023, Parav Pandit <parav@nvidia.com> wrote:
>>
>> >> From: Parav Pandit <parav@nvidia.com>
>> >> Sent: Friday, February 17, 2023 10:45 AM
>> >
>> >> Patch summary:
>> >> patch-1: consolidate read only field at one place in driver
>> >> requirements
>> >> patch-2: define device configuration layout before describing its fields.
>> >>
>> >> changelog:
>> >> v2->v3:
>> >> - split into two patches
>> >> - move read only description to driver requirements section
>> >
>> > These 2 patches are reviewed.
>> > Can you please open a ballot for it?
>> > Github issue:
>> > https://lists.oasis-open.org/archives/virtio-dev/202302/msg00405.html
>> > And the github description has the latest link this time. :)
>>
>> I think something went wrong here... the link above points to this series (i.e. not
>> the latest one), and so does the github issue, and therefore the ballot. I think we
>> should withdraw the ballot?
>
> Please withdraw.
>
> Right link is: [1].
> Please create the new ballot with link [1].
>
> [1] https://lists.oasis-open.org/archives/virtio-dev/202302/msg00556.html
Done.
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next prev parent reply other threads:[~2023-03-08 10:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 15:45 [virtio-comment] [PATCH v3 0/2] virtio-net: Improve dev config layout Parav Pandit
2023-02-17 15:45 ` [PATCH v3 1/2] virtio-net: Describe dev cfg fields read only Parav Pandit
2023-02-20 14:46 ` [virtio-dev] " David Edmondson
2023-02-21 15:37 ` [virtio-dev] " Cornelia Huck
2023-02-21 17:42 ` Michael S. Tsirkin
2023-02-21 17:50 ` Parav Pandit
2023-02-21 17:52 ` Michael S. Tsirkin
2023-02-21 17:59 ` Parav Pandit
2023-02-21 18:08 ` Michael S. Tsirkin
2023-02-22 9:01 ` [virtio-dev] " Cornelia Huck
2023-02-22 11:50 ` Michael S. Tsirkin
2023-02-22 12:07 ` [virtio-comment] " Cornelia Huck
2023-02-22 12:55 ` Michael S. Tsirkin
2023-02-22 13:26 ` [virtio-comment] " Cornelia Huck
2023-02-23 5:50 ` Parav Pandit
2023-02-17 15:45 ` [PATCH v3 2/2] virtio-net: Define cfg fields before description Parav Pandit
2023-02-20 14:42 ` [virtio-comment] " David Edmondson
2023-02-21 13:30 ` [PATCH v3 0/2] virtio-net: Improve dev config layout Parav Pandit
[not found] ` <875ybej6hb.fsf@redhat.com>
2023-03-07 17:25 ` [virtio-comment] " Parav Pandit
2023-03-07 17:25 ` [virtio-dev] " Parav Pandit
2023-03-08 10:07 ` Cornelia Huck [this message]
2023-03-08 10:07 ` [virtio-dev] Re: [virtio-comment] " Cornelia Huck
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=87lek7lfnv.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=mst@redhat.com \
--cc=parav@nvidia.com \
--cc=shahafs@nvidia.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.