[patch 0/7] CAN: Add new PF_CAN protocol family, try #3 · Urs Thuermann <hidden> · 2007-06-22
[patch 1/7] CAN: Allocate protocol numbers for PF_CAN · Urs Thuermann <hidden> · 2007-06-22
[patch 5/7] CAN: Add virtual CAN netdevice driver · Urs Thuermann <hidden> · 2007-06-22
Re: [patch 5/7] CAN: Add virtual CAN netdevice driver · Patrick McHardy <hidden> · 2007-06-22
[patch 3/7] CAN: Add raw protocol · Urs Thuermann <hidden> · 2007-06-22
[patch 6/7] CAN: Add maintainer entries · Urs Thuermann <hidden> · 2007-06-22
[patch 2/7] CAN: Add PF_CAN core module · Urs Thuermann <hidden> · 2007-06-22
[patch 4/7] CAN: Add broadcast manager (bcm) protocol · Urs Thuermann <hidden> · 2007-06-22
[patch 7/7] CAN: Add documentation · Urs Thuermann <hidden> · 2007-06-22
Re: [patch 0/7] CAN: Add new PF_CAN protocol family, try #3 · Patrick McHardy <hidden> · 2007-06-22
Re: [patch 0/7] CAN: Add new PF_CAN protocol family, try #3 · Oliver Hartkopp <hidden> · 2007-06-22
Re: [patch 0/7] CAN: Add new PF_CAN protocol family, try #3 · Patrick McHardy <hidden> · 2007-06-22
Re: [patch 0/7] CAN: Add new PF_CAN protocol family, try #3 · Oliver Hartkopp <hidden> · 2007-06-22

Re: [patch 5/7] CAN: Add virtual CAN netdevice driver

From: Patrick McHardy <hidden>
Date: 2007-06-22 11:03:09

Urs Thuermann wrote:

This patch adds the virtual CAN bus (vcan) network driver.
The vcan device is just a loopback device for CAN frames, no
real CAN hardware is involved.


Is there a reason why you're still doing the "allocate n devices
on init" thing instead of using the rtnl_link API?

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help