At 16:11 23/05/00 +0400, Oleg Sharoiko wrote:
>On Tue, 23 May 2000, Bob Bishop wrote:
>
>BB> FWIW -CURRENT is the same, but it looks like none of the calls check the
>BB> return value anyway.
>Well. There was a message during the boot of kernel which notified that
>"adv0 device prove/attach return
On Tue, 23 May 2000, Bob Bishop wrote:
BB> FWIW -CURRENT is the same, but it looks like none of the calls check the
BB> return value anyway.
Well. There was a message during the boot of kernel which notified that
"adv0 device prove/attach returned 1" (or smt. like this). So I think the
return cod
At 11:52 +0400 23/5/00, Oleg Sharoiko wrote:
>Hello!
>
>It seems that during porting to newbus architecture adv_attach was left
>unchanged and current version (I mean the current version of -STABLE
>sources, I didn't check -CURRENT) returns incorrect values (1 on success, 0 in
>all other cases).
Hi,
In article <[EMAIL PROTECTED]>
Oleg Sharoiko <[EMAIL PROTECTED]> writes:
> It seems that during porting to newbus architecture adv_attach was left
> unchanged and current version (I mean the current version of -STABLE
> sources, I didn't check -CURRENT) returns incorrect values (1 on success
Hello!
It seems that during porting to newbus architecture adv_attach was left
unchanged and current version (I mean the current version of -STABLE
sources, I didn't check -CURRENT) returns incorrect values (1 on success, 0 in
all other cases). I've fixed this, the patch is in the attached file.
5 matches
Mail list logo