Ar Gwe, 2006-06-30 am 14:02 +0200, ysgrifennodd Arjan van de Ven: > > Yes. I've been wondering if we should log the failure case somewhere, > > either as a tty-> object or printk. > > printk gets... interesting if you use serial console ;) > both locking and buffer space wise Not particularly. This is on the receive path not the transmit path so the locking considerations don't arise. Alan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- References:
- [PATCH] Airprime driver improvements to allow full speed EvDO transfers
- From: Andy Gay <[email protected]>
- Re: [PATCH] Airprime driver improvements to allow full speed EvDO transfers
- From: Andrew Morton <[email protected]>
- Re: [PATCH] Airprime driver improvements to allow full speed EvDO transfers
- From: Sergei Organov <[email protected]>
- Re: [linux-usb-devel] [PATCH] Airprime driver improvements to allow full speed EvDO transfers
- From: Alan Cox <[email protected]>
- Re: [linux-usb-devel] [PATCH] Airprime driver improvements to allow full speed EvDO transfers
- From: Arjan van de Ven <[email protected]>
- [PATCH] Airprime driver improvements to allow full speed EvDO transfers
- Prev by Date: Re: [PATCH 10/17] 2.6.17.1 perfmon2 patch for review: PMU context switch
- Next by Date: usb-storage device wrongly seen as "write protect is on"
- Previous by thread: Re: [linux-usb-devel] [PATCH] Airprime driver improvements to allow full speed EvDO transfers
- Next by thread: Re: [PATCH] Airprime driver improvements to allow full speed EvDO transfers
- Index(es):
 |