[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1d9a5ee9-779e-6255-08c6-b4f57af701a6@redhat.com>
Date: Wed, 27 Nov 2019 19:03:00 +0800
From: Jason Wang <jasowang@...hat.com>
To: Martin Habets <mhabets@...arflare.com>,
Parav Pandit <parav@...lanox.com>,
Jeff Kirsher <jeffrey.t.kirsher@...el.com>,
"davem@...emloft.net" <davem@...emloft.net>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>
Cc: Dave Ertman <david.m.ertman@...el.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
"nhorman@...hat.com" <nhorman@...hat.com>,
"sassmann@...hat.com" <sassmann@...hat.com>,
"jgg@...pe.ca" <jgg@...pe.ca>, Kiran Patil <kiran.patil@...el.com>,
"Michael S. Tsirkin" <mst@...hat.com>,
Alex Williamson <alex.williamson@...hat.com>,
"Bie, Tiwei" <tiwei.bie@...el.com>
Subject: Re: [net-next v2 1/1] virtual-bus: Implementation of Virtual Bus
On 2019/11/27 下午6:58, Jason Wang wrote:
>
>> With the virtual bus we do have a solid foundation going forward, for
>> the users we know now and for
>> future ones.
>
>
> If I understand correctly, if multiplexer is not preferred. It would
> be hard to have a bus on your own code, there's no much code could be
> reused.
>
Sorry, I meant "not hard to have" ...
Thanks
> Thanks
Powered by blists - more mailing lists