From: Greg KH [EMAIL PROTECTED]
Date: Fri, 5 May 2006 21:08:39 -0700
On Fri, May 05, 2006 at 06:41:58PM -0700, David S. Miller wrote:
From: Stephen Hemminger [EMAIL PROTECTED]
Date: Fri, 21 Apr 2006 12:54:38 -0700
Atomically create attributes when class device is added. This avoids the
On Fri, 05 May 2006 21:39:14 -0700
Ben Greear [EMAIL PROTECTED] wrote:
Andrew Morton wrote:
Sorry, I should have added Badalian to Cc:. He's using 3c905C (3c59x.c,
allegedly maintained by myself).
(Badalian, please use emailed reply-to-all rather than the bugzilla
interface for the
On Fri, May 05, 2006 at 05:16:46PM -0700, David S. Miller ([EMAIL PROTECTED])
wrote:
From: Evgeniy Polyakov [EMAIL PROTECTED]
Date: Thu, 4 May 2006 16:24:22 +0400
No in-kernel users require it to be exported, so if you do think it
should not be exported I will force external module
On Fri, May 05, 2006 at 05:35:33PM -0700, David S. Miller ([EMAIL PROTECTED])
wrote:
From: Evgeniy Polyakov [EMAIL PROTECTED]
Date: Fri, 5 May 2006 13:36:56 +0400
Hardware folks could also create it's own implementation and show
community if theirs approach is good or not.
Designing
On Sat, May 06, 2006 at 12:42:38PM +0400, Evgeniy Polyakov ([EMAIL PROTECTED])
wrote:
On Fri, May 05, 2006 at 05:35:33PM -0700, David S. Miller ([EMAIL PROTECTED])
wrote:
From: Evgeniy Polyakov [EMAIL PROTECTED]
Date: Fri, 5 May 2006 13:36:56 +0400
Hardware folks could also create
Can a bcm43xx user please test this. It uses the new txrate stuff found in
the wireless-dev tree.
Signed-off-by: Daniel Drake [EMAIL PROTECTED]
Index: linux/drivers/net/wireless/bcm43xx/bcm43xx_xmit.c
===
---
Hi:
These patches abstract out the protocol-specific encapsulation parts of
IPsec into what I've termed xfrm_mode objects. This allows us to share
a little bit more code. But more importantly, it allows us to add new
encapsulation modes such as BEET or v4/v6 and v6/v4 without polluting
the
Hi:
The number of locks used to manage afinfo structures can easily be reduced
down to one each for policy and state respectively. This is based on the
observation that the write locks are only held by module insertion/removal
which are very rare events so there is no need to further
Hi:
This patch adds the structure xfrm_mode. It is meant to represent
the operations carried out by transport/tunnel modes.
By doing this we allow additional encapsulation modes to be added
without clogging up the xfrm_input/xfrm_output paths.
Candidate modes include 4-to-6 tunnel mode, 6-to-4
Hi:
This patch is totally untested but shows how we can use xfrm_mode to
remove unnecessary code sharing between modes that in fact end up
slowing things down. In particular, notice how we've eliminated a
double IP header copying for tunnel mode which is in fact the common
case.
I need to
Hi,
While working on the rt2x00 driver, I keep hitting against some problems with
scanning.
Basicly the dscape stack handles scanning in 2 ways, through the
passive_scan() handler in the ieee80211_hw structure, and by calling
the config() handler in the ieee80211_hw stucture.
The usage of the
On Fri, May 05, 2006 at 09:12:09PM -0700, Stephen Hemminger wrote:
Linus Torvalds wrote:
On Fri, 5 May 2006, Andrew Morton wrote:
On Fri, 5 May 2006 21:06:18 -0400
John W. Linville [EMAIL PROTECTED] wrote:
These are fixes intended for 2.6.17...thanks!
Jeff is offline for a
Hi,
I'd like to print the TCP cwnd for the sender, with every packet before it is
sent out. This way i could plot the sender window over time to show TCP's
behavior in certain conditions.
I see in tcp_input.c several places where i could print the current window, but
i'd have to add code in
The classical IP over ATM code maintains its own IPv4 - ATM stuff
ARP table, using the standard neighbour-table code. The
neigh_table_init function adds this neighbour table to a linked
list of all neighbor tables which is used by the functions
neigh_delete() neigh_add() and neightbl_set(), all
Begin forwarded message:
Date: Sat, 6 May 2006 08:24:25 -0700
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [Bugme-new] [Bug 6502] New: SIOCSIFHWBROADCAST needs compat layer
http://bugzilla.kernel.org/show_bug.cgi?id=6502
Summary: SIOCSIFHWBROADCAST needs compat layer
In article [EMAIL PROTECTED] (at Sat, 06 May 2006 17:13:29 +0100), Simon
Kelley [EMAIL PROTECTED] says:
+void neigh_table_init(struct neigh_table *tbl)
+{
+ struct neigh_table *tmp;
+
+ neigh_table_init_no_netlink(tbl);
+ write_lock(neigh_tbl_lock);
+ for (tmp = neigh_tables; tmp; tmp
The classical IP over ATM code maintains its own IPv4 - ATM stuff
ARP table, using the standard neighbour-table code. The
neigh_table_init function adds this neighbour table to a linked
list of all neighbor tables which is used by the functions
neigh_delete() neigh_add() and neightbl_set(), all
Andrew Morton wrote:
I guess I can type simple commands and add printks. Do you have time to
take a look at the driver and suggest what I should be looking for?
I can only offer vague hints:
TX usually works, but RX often has isues. There is usually a bit
or two that needs setting to
On Friday 05 May 2006 21:59, Stefano Brivio wrote:
Fix whitespace.
Signed-off-by: Stefano Brivio [EMAIL PROTECTED]
Index: wireless-dev/drivers/net/wireless/bcm43xx/bcm43xx_main.c
===
---
TCP Low Priority is a distributed algorithm whose goal is to utilize only
the excess network bandwidth as compared to the ``fair share`` of
bandwidth as targeted by TCP. Available from:
http://www.ece.rice.edu/~akuzma/Doc/akuzma/TCP-LP.pdf
Original Author:
Aleksandar Kuzmanovic [EMAIL
On Fri, 2006-05-05 at 17:38 +0100, David Woodhouse wrote:
I still need this hack to work around the fact that softmac doesn't
attempt to associate when we bring the device up...
It'd be quite good to get this fixed in 2.6.17 too. Otherwise, the
device doesn't manage to associate if you use the
On Friday 05 May 2006 22:14, you wrote:
# Groups follow countries
#
Group 0 - Unspecified Country
#
# Band Ch. Range Ch. Spacing Power Flags
^
Aren't there countries around, where there are gaps in the
allowed channel numbers? (Especially for 802.11a) So
Michael Buesch wrote:
On Friday 05 May 2006 22:14, you wrote:
# Groups follow countries
#
Group 0 - Unspecified Country
#
# Band Ch. Range Ch. Spacing Power Flags
^
Aren't there countries around, where there are gaps in the
allowed channel numbers?
On Fri, May 05, 2006 at 11:00:50PM -0700, David S. Miller wrote:
From: Greg KH [EMAIL PROTECTED]
Date: Fri, 5 May 2006 21:08:39 -0700
On Fri, May 05, 2006 at 06:41:58PM -0700, David S. Miller wrote:
From: Stephen Hemminger [EMAIL PROTECTED]
Date: Fri, 21 Apr 2006 12:54:38 -0700
From: Greg KH [EMAIL PROTECTED]
Date: Sat, 6 May 2006 15:59:04 -0700
On Fri, May 05, 2006 at 11:00:50PM -0700, David S. Miller wrote:
The networking bit by Stephen is a bug fix.
Good point. Ok, feel free to send both patches to Linus now if you
want. You can add my:
Signed-off-by:
On Sat, 2006-05-06 at 11:39 +0900, YOSHIFUJI Hideaki wrote:
In article [EMAIL PROTECTED] (at Sat, 06 May 2006 01:53:21 +0100), David
Woodhouse [EMAIL PROTECTED] says:
There is a default route, because I believe that's the only thing that
radvd can do. I cannot advertise a route to _only_
On Sat, 2006-05-06 at 09:19 +0900, YOSHIFUJI Hideaki wrote:
You have compatible address.
Do you really use the tunnel? How did you configure it?
Sorry, I should have shown a strace from a different machine. Try this
one from an autoconfigured machine...
socket(PF_INET6, SOCK_DGRAM,
From: Stephen Hemminger [EMAIL PROTECTED]
Date: Fri, 21 Apr 2006 13:42:05 -0700
In case of sysfs failure, don't let device be brought up.
It can be cleared by unregister_netdevice so module can be unloaded
normally.
Signed-off-by: Stephen Hemminger [EMAIL PROTECTED]
I'm not so sure about
From: Stephen Hemminger [EMAIL PROTECTED]
Date: Mon, 24 Apr 2006 15:23:41 -0700
This follows after the earlier two patches.
Change the initialization of the class device portion of the net device
to be done earlier, so that any races before registration completes are
harmless. Add a mutex
From: Randy.Dunlap [EMAIL PROTECTED]
Date: Mon, 1 May 2006 15:31:34 -0700
Use NULL instead of 0 for a null pointer value (sparse warning):
drivers/net/irda/irda-usb.c:1781:30: warning: Using plain integer as NULL
pointer
Correct timeout argument to use milliseconds instead of jiffies.
Jouni Malinen wrote:
On Fri, May 05, 2006 at 03:14:35PM -0500, Larry Finger wrote:
The driver may not know the country code, so there should be mechanism
for user space to override this.
Do you think an environment variable would suffice, or do you propose another
scheme?
* Checksum
On Fri, 2006-05-05 at 10:28 -0700, Jean Tourrilhes wrote:
Note that the main limitation is that before I introduced the
explicit IW_QUAL_DBM in WE-19, the way to know if the value was
relative or dBm was to use the 'sign' of it, i.e. value above 0 were
non-dBm. The test is a few line
On Fri, May 05, 2006 at 02:57:26PM -0400, Andy Gospodarek wrote:
On Fri, May 05, 2006 at 12:20:54PM +0900, Horms wrote:
Sorry, I missunderstood your patch completely the first time around.
Yes I think this is an excellent idea. Assuming its tested and works
I'm happy to sign off on it
How many times are you going to post this same patch over and over
again? Please don't do that, thank you.
We all saw it the first time.
-
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
34 matches
Mail list logo
