virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Matias Ezequiel Vara Larsen <mvaralar@redhat.com>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: Harald Mommer <harald.mommer@opensynergy.com>,
	Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
	Mikhail Golubev-Ciuchea <Mikhail.Golubev-Ciuchea@opensynergy.com>,
	Wolfgang Grandegger <wg@grandegger.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Jason Wang <jasowang@redhat.com>,
	Xuan Zhuo <xuanzhuo@linux.alibaba.com>,
	Damir Shaikhutdinov <Damir.Shaikhutdinov@opensynergy.com>,
	linux-kernel@vger.kernel.org, linux-can@vger.kernel.org,
	netdev@vger.kernel.org, virtualization@lists.linux.dev
Subject: Re: [PATCH v5] can: virtio: Initial virtio CAN driver.
Date: Wed, 12 Mar 2025 14:28:10 +0100	[thread overview]
Message-ID: <Z9GL6o01fuhTbHWO@fedora> (raw)
In-Reply-To: <20250312-conscious-sloppy-pegasus-b5099d-mkl@pengutronix.de>

On Wed, Mar 12, 2025 at 11:41:26AM +0100, Marc Kleine-Budde wrote:
> On 12.03.2025 11:31:12, Matias Ezequiel Vara Larsen wrote:
> > On Thu, Feb 01, 2024 at 07:57:45PM +0100, Harald Mommer wrote:
> > > Hello,
> > > 
> > > I thought there would be some more comments coming and I could address
> > > everything in one chunk. Not the case, besides your comments silence.
> > > 
> > > On 08.01.24 20:34, Christophe JAILLET wrote:
> > > > 
> > > > Hi,
> > > > a few nits below, should there be a v6.
> > > > 
> > > 
> > > I'm sure there will be but not so soon. Probably after acceptance of the
> > > virtio CAN specification or after change requests to the specification are
> > > received and the driver has to be adapted to an updated draft.
> > > 
> > What is the status of this series?
> 
> There has been no movement from the Linux side. The patch series is
> quite extensive. To get this mainline, we need not only a proper Linux
> CAN driver, but also a proper VirtIO specification. 

Thanks for your answer. AFAIK the spec has been merged (see
https://github.com/oasis-tcs/virtio-spec/tree/virtio-1.4). 

> This whole project is too big for me to do it as a collaborative
> effort.
> 

What do you mean?

Thanks, 

Matias


  reply	other threads:[~2025-03-12 13:28 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-08 13:10 [PATCH v5] can: virtio: Initial virtio CAN driver Mikhail Golubev-Ciuchea
2024-01-08 19:34 ` Christophe JAILLET
2024-02-01 18:57   ` Harald Mommer
2025-03-12 10:31     ` Matias Ezequiel Vara Larsen
2025-03-12 10:41       ` Marc Kleine-Budde
2025-03-12 13:28         ` Matias Ezequiel Vara Larsen [this message]
2025-03-12 13:36           ` Marc Kleine-Budde
2025-03-12 15:11             ` Matias Ezequiel Vara Larsen
2025-03-13  0:26             ` Jason Wang
2025-03-13 18:48     ` Matias Ezequiel Vara Larsen
2025-09-11 20:59 ` Francesco Valla
2025-10-01 15:23   ` Matias Ezequiel Vara Larsen
2025-10-10 15:46   ` Matias Ezequiel Vara Larsen
2025-10-10 21:20     ` Francesco Valla
2025-10-13  9:52       ` Matias Ezequiel Vara Larsen
2025-10-13 16:29         ` Francesco Valla
2025-10-13 18:07           ` Matias Ezequiel Vara Larsen
2025-10-13 14:15       ` Matias Ezequiel Vara Larsen
2025-10-13 16:35   ` Matias Ezequiel Vara Larsen
2025-10-14  6:54     ` Francesco Valla
2025-10-14 10:42       ` Matias Ezequiel Vara Larsen
2025-10-14 10:15   ` Matias Ezequiel Vara Larsen
2025-10-14 16:01     ` Francesco Valla
2025-10-20 14:56       ` Matias Ezequiel Vara Larsen
2025-10-20 21:24         ` Francesco Valla
2025-10-21  9:40           ` Matias Ezequiel Vara Larsen
2025-10-21 12:08             ` Francesco Valla
2025-10-21 13:15               ` Matias Ezequiel Vara Larsen
2025-10-31 12:21                 ` Matias Ezequiel Vara Larsen
2025-10-14 10:25   ` Matias Ezequiel Vara Larsen

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=Z9GL6o01fuhTbHWO@fedora \
    --to=mvaralar@redhat.com \
    --cc=Damir.Shaikhutdinov@opensynergy.com \
    --cc=Mikhail.Golubev-Ciuchea@opensynergy.com \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=harald.mommer@opensynergy.com \
    --cc=jasowang@redhat.com \
    --cc=kuba@kernel.org \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=virtualization@lists.linux.dev \
    --cc=wg@grandegger.com \
    --cc=xuanzhuo@linux.alibaba.com \
    /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;
as well as URLs for NNTP newsgroup(s).