Re: Why /sys/class/net/*/features is read-only?

netdev

Re: Why /sys/class/net/*/features is read-only?

To:	util@xxxxxxxxxxxxxxx
Subject:	Re: Why /sys/class/net/*/features is read-only?
From:	"David S. Miller" <davem@xxxxxxxxxxxxx>
Date:	Mon, 23 May 2005 14:51:12 -0700 (PDT)
Cc:	shemminger@xxxxxxxx, netdev@xxxxxxxxxxx
In-reply-to:	<Pine.LNX.4.62.0505240032480.17855@xxxxxxxxxxxxxxxxxxx>
References:	<Pine.LNX.4.62.0505232346310.17855@xxxxxxxxxxxxxxxxxxx> <20050523.135348.55831423.davem@xxxxxxxxxxxxx> <Pine.LNX.4.62.0505240032480.17855@xxxxxxxxxxxxxxxxxxx>
Sender:	netdev-bounce@xxxxxxxxxxx

From: "Catalin(ux aka Dino) BOIE" <util@xxxxxxxxxxxxxxx>
Date: Tue, 24 May 2005 00:33:14 +0300 (EEST)

> On Mon, 23 May 2005, David S. Miller wrote:
> 
> > Let them use ethtool :-)
> 
> They can't on a bridge device, right?

Currently no.  But there is no reason the bridge device
should not have ethtool support added to it, and that's
where this functionality belongs.

[More with this subject...]

<Prev in Thread]	Current Thread	[Next in Thread>
*Why /sys/class/net//features is read-only?*, Catalin(ux aka Dino) BOIE* *Re: Why /sys/class/net//features is read-only?*, Stephen Hemminger* *Re: Why /sys/class/net//features is read-only?*, Catalin(ux aka Dino) BOIE* *Re: Why /sys/class/net//features is read-only?*, David S. Miller* *Re: Why /sys/class/net//features is read-only?*, Catalin(ux aka Dino) BOIE* *Re: Why /sys/class/net//features is read-only?*, David S. Miller* <= *Re: Why /sys/class/net//features is read-only?*, Catalin(ux aka Dino) BOIE* *Re: Why /sys/class/net//features is read-only?*, Stephen Hemminger*

Previous by Date:	Re: [PATCH] Super TSO v3, David S. Miller
Next by Date:	Re: [PATCH linux-2.6.12-rc4-mm1] ethtool: Add NETIF_F_HW_CSUM support, Stephen Hemminger
Previous by Thread:	*Re: Why /sys/class/net//features is read-only?*, Catalin(ux aka Dino) BOIE*
Next by Thread:	*Re: Why /sys/class/net//features is read-only?*, Catalin(ux aka Dino) BOIE*
Indexes:	[Date] [Thread] [Top] [All Lists]