netdev
[Top] [All Lists]

Re: [PATCH] NETIF_F_LLTX for devices 2

To: Andi Kleen <ak@xxxxxxx>
Subject: Re: [PATCH] NETIF_F_LLTX for devices 2
From: Jeff Garzik <jgarzik@xxxxxxxxx>
Date: Sun, 12 Sep 2004 12:16:05 -0400
Cc: "David S. Miller" <davem@xxxxxxxxxxxxx>, hadi@xxxxxxxxxx, herbert@xxxxxxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx
In-reply-to: <20040912102529.GA27096@xxxxxxxxxxxxx>
References: <E1C4wYe-0005qT-00@xxxxxxxxxxxxxxxxxxxxxxxx> <20040908072408.GI27886@xxxxxxxxxxxxx> <1094629677.1089.155.camel@xxxxxxxxxxxxxxxx> <20040908134713.1bcd46d3.davem@xxxxxxxxxxxxx> <1094823215.1121.129.camel@xxxxxxxxxxxxxxxx> <20040911142116.GL4431@xxxxxxxxxxxxx> <1094933731.2343.109.camel@xxxxxxxxxxxxxxxx> <20040911174535.2acbb957.davem@xxxxxxxxxxxxx> <20040912100114.GB11484@xxxxxxxxxxxxx> <20040912102529.GA27096@xxxxxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mutt/1.4.1i
On Sun, Sep 12, 2004 at 12:25:29PM +0200, Andi Kleen wrote:
> On Sun, Sep 12, 2004 at 06:01:14AM -0400, Jeff Garzik wrote:
> > 
> > Oh and update Documentation/networking/netdevice.txt.
> > 
> > If people are going to screw with the TX path, at least do it right and
> > make it non-mysterious for everyone else.
> > 
> > See Al Viro's Documentation/filesystem/directory-locking doc for a
> > proper way to document a locking change that potentially affects every
> > net driver in the kernel.
> 
> <broken record mode>
> No it doesn't. It only affects every driver who sets NETIF_F_LLTX.
> For drivers that don't set this flag there is no change at all. 
> </record>

Incorrect, you are changing the callsites, which -does- affect every
driver.


> I wasn't aware of Documentation/netdevices.txt, but I agree it 
> would be a good idea to update it. Patch for that attached.
> DaveM, please apply.

Thanks, but still need a patch for return value constants, otherwise you
are compounding rather than addressing a current problem.

        Jeff




<Prev in Thread] Current Thread [Next in Thread>