aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/char/ip2
diff options
context:
space:
mode:
authorRusty Russell <rusty@rustcorp.com.au>2010-08-04 17:32:05 +0000
committerDavid S. Miller <davem@davemloft.net>2010-08-04 21:53:17 -0700
commita767bde4d484b60dab0abac740a7151b624a30bf (patch)
tree9caf3dcf83afcc332012f0b551144a79955ff3d6 /drivers/char/ip2
parentd7100da026317fcf07411f765fe1cdb044053917 (diff)
downloadkernel_samsung_crespo-a767bde4d484b60dab0abac740a7151b624a30bf.zip
kernel_samsung_crespo-a767bde4d484b60dab0abac740a7151b624a30bf.tar.gz
kernel_samsung_crespo-a767bde4d484b60dab0abac740a7151b624a30bf.tar.bz2
virtio_net: implements ethtool_ops.get_drvinfo
I often use "ethtool -i" command to check what driver controls the ehternet device. But because current virtio_net driver doesn't support "ethtool -i", it becomes the following: # ethtool -i eth3 Cannot get driver information: Operation not supported This patch simply adds the "ethtool -i" support. The following is the result when using the virtio_net driver with my patch applied to. # ethtool -i eth3 driver: virtio_net version: N/A firmware-version: N/A bus-info: virtio0 Personally, "-i" is one of the most frequently-used option, and most network drivers support "ethtool -i", so I think virtio_net also should do. Signed-off-by: Taku Izumi <izumi.taku@jp.fujitsu.com> Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (use ARRAY_SIZE) Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/char/ip2')
0 files changed, 0 insertions, 0 deletions