netdev
[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

Re: [PATCH] NETIF_F_LLTX for devices 2

from [Jeff Garzik] [Permanent Link][Original]
To: "David S. Miller" <davem@xxxxxxxxxxxxx>
Subject: Re: [PATCH] NETIF_F_LLTX for devices 2
From: Jeff Garzik <jgarzik@xxxxxxxxx>
Date: Sun, 12 Sep 2004 06:01:14 -0400
Cc: hadi@xxxxxxxxxx, ak@xxxxxxx, herbert@xxxxxxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx
In-reply-to: <20040911174535.2acbb957.davem@xxxxxxxxxxxxx>
References: <20040908065152.GC27886@xxxxxxxxxxxxx> <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>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mutt/1.4.1i 
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.

        Jeff
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  Re: [PATCH] NETIF_F_LLTX for devices 2, Jeff Garzik
Next by Date:  Re: [PATCH] NETIF_F_LLTX for devices 2, Andi Kleen
Previous by Thread:  Re: [PATCH] NETIF_F_LLTX for devices 2, Jeff Garzik
Next by Thread:  Re: [PATCH] NETIF_F_LLTX for devices 2, Andi Kleen
Indexes:  [Date] [Thread] [Top] [All Lists]