Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[Prism54\-devel\]\s+Re\:\s+\[PATCH\s+0\/14\]\s+prism54\:\s+bring\s+up\s+to\s+sync\s+with\s+prism54\.org\s+cvs\s+rep\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[Prism54\-devel\]\s+Re\:\s+\[PATCH\s+0\/14\]\s+prism54\:\s+bring\s+up\s+to\s+sync\s+with\s+prism54\.org\s+cvs\s+rep\s*$/: 10 ]

Total 10 documents matching your query.

1. rep (score: 1): Author: Jeff Garzik <jgarzik@xxxxxxxxx>; Date: Thu, 27 May 2004 14:25:31 -0400; Please at least apply the changes in the "8/14" patch, because without them the driver is unusable on big-endian architectures.; /archives/netdev/2004-05/msg00403.html (10,647 bytes)
2. uts (score: 1): Author: >; Date: Thu, 27 May 2004 12:05:44 -0700; Whitespace changes are often nice, but they should be the very first patch[es] in the series. You should be able to verify that the .o file was unchanged before and after. That way they become a no-b; /archives/netdev/2004-05/msg00406.html (9,998 bytes)
3. ad? (score: 1): Author: bar@xxxxxxxxxx>; Date: Thu, 27 May 2004 15:45:13 -0400; Great. I'll fix all those patches up again for you and Marcelo. For future development I've asked other prism54 developers to first send patches to netdev for review/approval. Maybe we *should* do aw; /archives/netdev/2004-05/msg00415.html (12,299 bytes)
4. in (score: 1): Author: xxxx (Luis R. Rodriguez); Date: Thu, 27 May 2004 16:04:14 -0400; Will do. My plan was for us to get the pathes for 2.6 all set. Once we were all happy and our trees in sync we'd send a large 2.4 patch for inclusion in 2.4 OK. Sure thing. I think we should. Anyone; /archives/netdev/2004-05/msg00417.html (11,397 bytes)
5. ing (score: 1): Author: urovegin <ebs@xxxxxxxxxxx>; Date: Sat, 29 May 2004 04:38:03 -0400; Please do. Good luck. Jeff, Since Margit is working on touching up her compat work she'll just submit the patches. -- GnuPG Key fingerprint = 113F B290 C6D2 0251 4D84 A34A 6ADD 4937 E20A 525E Attachm; /archives/netdev/2004-05/msg00447.html (9,328 bytes)
6. Re: [Prism54-devel] Re: [PATCH 0/14] prism54: bring up to sync with prism54.org cvs rep (score: 1): Author: Clint Adams <schizo@xxxxxxxxxx>; Date: Thu, 27 May 2004 14:25:31 -0400; Please at least apply the changes in the "8/14" patch, because without them the driver is unusable on big-endian architectures.; /archives/netdev/2004-05/msg00921.html (10,724 bytes)
7. Re: [Prism54-devel] Re: [PATCH 0/14] prism54: bring up to sync with prism54.org cvs rep (score: 1): Author: Andrew Morton <akpm@xxxxxxxx>; Date: Thu, 27 May 2004 12:05:44 -0700; Whitespace changes are often nice, but they should be the very first patch[es] in the series. You should be able to verify that the .o file was unchanged before and after. That way they become a no-b; /archives/netdev/2004-05/msg00924.html (10,184 bytes)
8. Re: [Prism54-devel] Re: [PATCH 0/14] prism54: bring up to sync with prism54.org cvs rep (score: 1): Author: mcgrof@xxxxxxxxxxxxxxxxxxxx (Luis R. Rodriguez); Date: Thu, 27 May 2004 15:45:13 -0400; Great. I'll fix all those patches up again for you and Marcelo. For future development I've asked other prism54 developers to first send patches to netdev for review/approval. Maybe we *should* do aw; /archives/netdev/2004-05/msg00933.html (12,543 bytes)
9. Re: [Prism54-devel] Re: [PATCH 0/14] prism54: bring up to sync with prism54.org cvs rep (score: 1): Author: mcgrof@xxxxxxxxxxxxxxxxxxxx (Luis R. Rodriguez); Date: Thu, 27 May 2004 16:04:14 -0400; Will do. My plan was for us to get the pathes for 2.6 all set. Once we were all happy and our trees in sync we'd send a large 2.4 patch for inclusion in 2.4 OK. Sure thing. I think we should. Anyone; /archives/netdev/2004-05/msg00935.html (11,722 bytes)
10. Re: [Prism54-devel] Re: [PATCH 0/14] prism54: bring up to sync with prism54.org cvs rep (score: 1): Author: mcgrof@xxxxxxxxxxxxxxxxxxxx (Luis R. Rodriguez); Date: Sat, 29 May 2004 04:38:03 -0400; Please do. Good luck. Jeff, Since Margit is working on touching up her compat work she'll just submit the patches. -- GnuPG Key fingerprint = 113F B290 C6D2 0251 4D84 A34A 6ADD 4937 E20A 525E Attachm; /archives/netdev/2004-05/msg00965.html (9,468 bytes)

Current List: 1 - 10
Page: [1]