Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Steps\s+for\s+netdev\-2\.6\s+inclusion\?\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Steps\s+for\s+netdev\-2\.6\s+inclusion\?\s*$/: 12 ]

Total 12 documents matching your query.

1. Re: Steps for netdev-2.6 inclusion? (score: 1): Author: James Ketrenos <jketreno@xxxxxxxxxxxxxxx>; Date: Thu, 06 Jan 2005 10:10:50 -0600; Jeff Garzik wrote: James Ketrenos wrote: Ok, its been a long time coming, but it appears the ipw* wireless drivers are to the point where being more proactive at getting them into the kernel is appro; /archives/netdev/2005-01/msg00165.html (8,600 bytes)
2. n.c [PATCH] (score: 1): Author: James Ketrenos <jketreno@xxxxxxxxxxxxxxx>; Date: Wed, 01 Dec 2004 19:34:59 -0600; s against the 2.6.8.1 kernel tree. Cheers, Shaun 2004-1; /archives/netdev/2004-12/msg00015.html (9,593 bytes)
3. ssion limit (score: 1): Author: Jeff Garzik <jgarzik@xxxxxxxxx>; Date: Thu, 02 Dec 2004 01:18:32 -0500; ference with DMA transactions? In addition to my patch,; /archives/netdev/2004-12/msg00018.html (8,295 bytes)
4. ces Rev 2.0 (score: 1): Author: James Ketrenos <jketreno@xxxxxxxxxxxxxxx>; Date: Thu, 02 Dec 2004 14:11:52 -0600; Y as autoneg or forced speeds. -- Jason McMullan <jason; /archives/netdev/2004-12/msg00033.html (11,493 bytes)
5. ute - Howto (score: 1): Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>; Date: Fri, 3 Dec 2004 10:33:39 +0000; would like to know. 1. What are the features currently; /archives/netdev/2004-12/msg00044.html (8,970 bytes)
6. (score: 1): Author: roadbent" <markb@xxxxxxxxxxxxxx>; Date: Tue, 21 Dec 2004 15:03:15 -0500; his code in tcp_output.c... int tcp_retransmit_skb(struct sock *sk, struct sk_buff *skb) { struct tcp_opt *tp = tcp_sk(sk); unsigned int cur_mss = tcp_current_; /archives/netdev/2004-12/msg00604.html (8,297 bytes)
7. Re: Steps for netdev-2.6 inclusion? (score: 1): Author: James Ketrenos <jketreno@xxxxxxxxxxxxxxx>; Date: Thu, 06 Jan 2005 10:10:50 -0600; Ok, its been a long time coming, but it appears the ipw* wireless drivers are to the point where being more proactive at getting them into the kernel is appropriate (at least based on the frequency; /archives/netdev/2005-01/msg01655.html (8,804 bytes)
8. Steps for netdev-2.6 inclusion? (score: 1): Author: James Ketrenos <jketreno@xxxxxxxxxxxxxxx>; Date: Wed, 01 Dec 2004 19:34:59 -0600; Ok, its been a long time coming, but it appears the ipw* wireless drivers are to the point where being more proactive at getting them into the kernel is appropriate (at least based on the frequency o; /archives/netdev/2004-12/msg00966.html (10,069 bytes)
9. Re: Steps for netdev-2.6 inclusion? (score: 1): Author: Jeff Garzik <jgarzik@xxxxxxxxx>; Date: Thu, 02 Dec 2004 01:18:32 -0500; It's fairly easy, just email me and netdev the patch for inclusion, and it'll get reviewed. Once review issues are addressed, I'll merge it immediately, which causes it to be automatically propagated; /archives/netdev/2004-12/msg00969.html (8,389 bytes)
10. Re: Steps for netdev-2.6 inclusion? (score: 1): Author: James Ketrenos <jketreno@xxxxxxxxxxxxxxx>; Date: Thu, 02 Dec 2004 14:11:52 -0600; It's fairly easy, just email me and netdev the patch for inclusion, and it'll get reviewed. Should I break the patch into the three components (ipw2100, ipw2200, and ieee80211) ? or just one huge pat; /archives/netdev/2004-12/msg00984.html (11,974 bytes)
11. Re: Steps for netdev-2.6 inclusion? (score: 1): Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>; Date: Fri, 3 Dec 2004 10:33:39 +0000; Please split it in three parts. And most importantly integrate your ieee80211 code with the hostap code in Jeff's queue, we really don't want two copies of it. The problem is again that the license f; /archives/netdev/2004-12/msg00995.html (9,064 bytes)
12. Re: Steps for netdev-2.6 inclusion? (score: 1): Author: Jeff Garzik <jgarzik@xxxxxxxxx>; Date: Tue, 21 Dec 2004 15:03:15 -0500; Ok, its been a long time coming, but it appears the ipw* wireless drivers are to the point where being more proactive at getting them into the kernel is appropriate (at least based on the frequency o; /archives/netdev/2004-12/msg01555.html (8,407 bytes)

Current List: 1 - 12
Page: [1]