Re: Typo in labpc.c

2000-11-19 Thread Julian Elischer
Peter Dufault wrote: This seems to only do the cdevsw_add if the malloc failed. I presume this is the opposit of the intended sense. I'll fix it up if you also think it looks wrong. If nobody have noticed in "17 months, 2 weeks ago" (as cvs-web says) that labpc doesn't work,

Re: Typo in labpc.c

2000-11-19 Thread Peter Dufault
For the record: If anyone wants labpc tested and kept up to date send me a card and I'll test it at each stable release cycle. Even better, also send me the register compatible DAQCARD 1200 PC card version. My former client using a batch of those cards obviously isn't staying up to

Re: Typo in labpc.c

2000-11-19 Thread Julian Elischer
Peter Dufault wrote: For the record: If anyone wants labpc tested and kept up to date send me a card and I'll test it at each stable release cycle. Even better, also send me the register compatible DAQCARD 1200 PC card version. My former client using a batch of those cards

Re: Typo in labpc.c

2000-11-18 Thread Poul-Henning Kamp
In message [EMAIL PROTECTED], David Malone writes: I noticed the following while looking through the M_ZERO patches. When you were cleaning up some dev stuff you made the following change to labpc.c (revision 1.33): labpcs = malloc(NLABPC * sizeof(struct ctlr *), M_DEVBUF, M_NOWAIT);

Re: Typo in labpc.c

2000-11-18 Thread Julian Elischer
Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], David Malone writes: I noticed the following while looking through the M_ZERO patches. When you were cleaning up some dev stuff you made the following change to labpc.c (revision 1.33): labpcs = malloc(NLABPC *