From: Cornelia Huck <cohuck@redhat.com>
To: Mikhail Golubev-Ciuchea <mikhail.golubev-ciuchea@opensynergy.com>,
virtio-comment@lists.oasis-open.org,
virtio-dev@lists.oasis-open.org, linux-can@vger.kernel.org
Cc: Harald Mommer <harald.mommer@opensynergy.com>
Subject: Re: [virtio-comment] [RFC PATCH v3] virtio-can: Device specification.
Date: Mon, 15 Jan 2024 17:24:08 +0100 [thread overview]
Message-ID: <87ttnemuon.fsf@redhat.com> (raw)
In-Reply-To: <ebc57e36-d822-4264-a763-b530482b2669@opensynergy.com>
On Mon, Jan 08 2024, Mikhail Golubev-Ciuchea <mikhail.golubev-ciuchea@opensynergy.com> wrote:
> Hi all!
>
> I kindly request a vote.
>
> Fixes: https://github.com/oasis-tcs/virtio-spec/issues/186
Oh, that has been a while... I believe that this still fits on top,
although it has conflicts with virtio-spi, but nothing that a bit of
fiddling can't sort out.
The main problem is that we're currently in a bit of an unfortunate
situation regarding voting: There's still a twice-postponed migration of
the OASIS infrastructure coming up, and I don't want to risk the voting
period being affected by an outage... hopefully we'll get a new schedule
soon.
In the meanwhile, if anyone could spare a few cycles looking at this,
it'd be appreciated. Nothing jumped out at me, but I'm not a CAN expert;
I'd be happy to open voting but for the looming migration issue.
WARNING: multiple messages have this Message-ID (diff)
From: Cornelia Huck <cohuck@redhat.com>
To: Mikhail Golubev-Ciuchea <mikhail.golubev-ciuchea@opensynergy.com>,
virtio-comment@lists.oasis-open.org,
virtio-dev@lists.oasis-open.org, linux-can@vger.kernel.org
Cc: Harald Mommer <harald.mommer@opensynergy.com>
Subject: Re: [virtio-comment] [RFC PATCH v3] virtio-can: Device specification.
Date: Mon, 15 Jan 2024 17:24:08 +0100 [thread overview]
Message-ID: <87ttnemuon.fsf@redhat.com> (raw)
In-Reply-To: <ebc57e36-d822-4264-a763-b530482b2669@opensynergy.com>
On Mon, Jan 08 2024, Mikhail Golubev-Ciuchea <mikhail.golubev-ciuchea@opensynergy.com> wrote:
> Hi all!
>
> I kindly request a vote.
>
> Fixes: https://github.com/oasis-tcs/virtio-spec/issues/186
Oh, that has been a while... I believe that this still fits on top,
although it has conflicts with virtio-spi, but nothing that a bit of
fiddling can't sort out.
The main problem is that we're currently in a bit of an unfortunate
situation regarding voting: There's still a twice-postponed migration of
the OASIS infrastructure coming up, and I don't want to risk the voting
period being affected by an outage... hopefully we'll get a new schedule
soon.
In the meanwhile, if anyone could spare a few cycles looking at this,
it'd be appreciated. Nothing jumped out at me, but I'm not a CAN expert;
I'd be happy to open voting but for the looming migration issue.
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: Mikhail Golubev-Ciuchea <mikhail.golubev-ciuchea@opensynergy.com>,
virtio-comment@lists.oasis-open.org,
virtio-dev@lists.oasis-open.org, linux-can@vger.kernel.org
Cc: Harald Mommer <harald.mommer@opensynergy.com>
Subject: [virtio-dev] Re: [virtio-comment] [RFC PATCH v3] virtio-can: Device specification.
Date: Mon, 15 Jan 2024 17:24:08 +0100 [thread overview]
Message-ID: <87ttnemuon.fsf@redhat.com> (raw)
In-Reply-To: <ebc57e36-d822-4264-a763-b530482b2669@opensynergy.com>
On Mon, Jan 08 2024, Mikhail Golubev-Ciuchea <mikhail.golubev-ciuchea@opensynergy.com> wrote:
> Hi all!
>
> I kindly request a vote.
>
> Fixes: https://github.com/oasis-tcs/virtio-spec/issues/186
Oh, that has been a while... I believe that this still fits on top,
although it has conflicts with virtio-spi, but nothing that a bit of
fiddling can't sort out.
The main problem is that we're currently in a bit of an unfortunate
situation regarding voting: There's still a twice-postponed migration of
the OASIS infrastructure coming up, and I don't want to risk the voting
period being affected by an outage... hopefully we'll get a new schedule
soon.
In the meanwhile, if anyone could spare a few cycles looking at this,
it'd be appreciated. Nothing jumped out at me, but I'm not a CAN expert;
I'd be happy to open voting but for the looming migration issue.
---------------------------------------------------------------------
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:[~2024-01-15 16:24 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 14:22 [RFC PATCH v3] virtio-can: Device specification Mikhail Golubev-Ciuchea
2023-06-09 14:22 ` [virtio-dev] " Mikhail Golubev-Ciuchea
2023-06-09 14:22 ` [virtio-comment] " Mikhail Golubev-Ciuchea
2024-01-08 17:18 ` Mikhail Golubev-Ciuchea
2024-01-08 17:18 ` [virtio-dev] " Mikhail Golubev-Ciuchea
2024-01-08 17:18 ` Mikhail Golubev-Ciuchea
2024-01-15 16:24 ` Cornelia Huck [this message]
2024-01-15 16:24 ` [virtio-dev] " Cornelia Huck
2024-01-15 16:24 ` Cornelia Huck
2024-02-02 12:45 ` Cornelia Huck
2024-02-02 12:45 ` [virtio-dev] " Cornelia Huck
2024-02-02 12:45 ` Cornelia Huck
2024-02-20 12:19 ` Matias Ezequiel Vara Larsen
2024-02-20 12:19 ` [virtio-dev] " Matias Ezequiel Vara Larsen
2024-02-20 12:19 ` Matias Ezequiel Vara Larsen
2024-02-21 15:42 ` Mikhail Golubev-Ciuchea
2024-02-21 15:42 ` [virtio-dev] " Mikhail Golubev-Ciuchea
2024-02-21 15:42 ` Mikhail Golubev-Ciuchea
2024-02-22 11:30 ` Matias Ezequiel Vara Larsen
2024-02-22 11:30 ` [virtio-dev] " Matias Ezequiel Vara Larsen
2024-02-22 11:30 ` Matias Ezequiel Vara Larsen
2024-02-21 10:37 ` Matias Ezequiel Vara Larsen
2024-02-21 10:37 ` [virtio-dev] " Matias Ezequiel Vara Larsen
2024-02-21 10:37 ` Matias Ezequiel Vara Larsen
2024-02-21 12:49 ` Marc Kleine-Budde
2024-02-21 12:49 ` [virtio-dev] " Marc Kleine-Budde
2024-02-21 13:16 ` Matias Ezequiel Vara Larsen
2024-02-21 13:16 ` Matias Ezequiel Vara Larsen
2024-02-21 13:16 ` [virtio-comment] " Matias Ezequiel Vara Larsen
2024-02-21 13:28 ` Marc Kleine-Budde
2024-02-26 12:36 ` Cornelia Huck
2024-02-26 12:36 ` Cornelia Huck
2024-02-26 12:36 ` [virtio-comment] " Cornelia Huck
2024-02-27 9:02 ` Matias Ezequiel Vara Larsen
2024-02-27 9:02 ` Matias Ezequiel Vara Larsen
2024-02-27 9:02 ` [virtio-comment] " Matias Ezequiel Vara Larsen
2024-03-06 14:12 ` Matias Ezequiel Vara Larsen
2024-02-13 14:57 ` [virtio-dev] " Cornelia Huck
2024-02-13 14:57 ` Cornelia Huck
2024-02-13 14:57 ` [virtio-comment] " Cornelia Huck
2024-02-16 11:08 ` Cornelia Huck
2024-02-16 11:08 ` Cornelia Huck
2024-02-16 11:08 ` [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=87ttnemuon.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=harald.mommer@opensynergy.com \
--cc=linux-can@vger.kernel.org \
--cc=mikhail.golubev-ciuchea@opensynergy.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.