Jeff Garzik wrote:
>
> Andrew Morton wrote:
> > Having stared sleepily at the code for several evenings I see no way in
> > which serial_driver.refcount can be non-zero while serial.o's module
> > refcount is zero. But it happened.
>
> Is it possible to replace serial_driver.refcount with
Jeff Garzik wrote:
Andrew Morton wrote:
Having stared sleepily at the code for several evenings I see no way in
which serial_driver.refcount can be non-zero while serial.o's module
refcount is zero. But it happened.
Is it possible to replace serial_driver.refcount with calls to
Andrew Morton wrote:
> Having stared sleepily at the code for several evenings I see no way in
> which serial_driver.refcount can be non-zero while serial.o's module
> refcount is zero. But it happened.
Is it possible to replace serial_driver.refcount with calls to
GET_USE_COUNT()? No need to
Marco d'Itri wrote:
>
> At the end of a UUCP poll this message was logged:
>
> Sep 19 23:42:47 wonderland kernel: Warning: null TTY for (04:40) in tty_fasync
>
> What does it mean?
>
Very hard to say.
Ted, Google says this has only been reported three or four times. Could
we please have a
Marco d'Itri wrote:
At the end of a UUCP poll this message was logged:
Sep 19 23:42:47 wonderland kernel: Warning: null TTY for (04:40) in tty_fasync
What does it mean?
Very hard to say.
Ted, Google says this has only been reported three or four times. Could
we please have a BUG()
5 matches
Mail list logo