Russell King wrote:
NAK. This means that you change the list of ports available on the machine to be limited to only those which are currently open. Utterly useless for debugging, where you normally want people to dump the contents of /proc/tty/driver/*. The original patch was better.
Is the original patch sufficient? or is there anything we should correct?
Taku Izumi <[email protected]> - 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/
- Follow-Ups:
- Re: [PATCH][BUG] Fix possible NULL pointer access in 8250 serial driver
- From: Andrew Morton <[email protected]>
- Re: [PATCH][BUG] Fix possible NULL pointer access in 8250 serial driver
- References:
- [PATCH][BUG] Fix possible NULL pointer access in 8250 serial driver
- From: izumi <[email protected]>
- Re: [PATCH][BUG] Fix possible NULL pointer access in 8250 serial driver
- From: Andrew Morton <[email protected]>
- Re: [PATCH][BUG] Fix possible NULL pointer access in 8250 serial driver
- From: Kenji Kaneshige <[email protected]>
- Re: [PATCH][BUG] Fix possible NULL pointer access in 8250 serial driver
- From: Russell King <[email protected]>
- [PATCH][BUG] Fix possible NULL pointer access in 8250 serial driver
- Prev by Date: Re: [Announce] [patch] Modular Scheduler Core and Completely Fair Scheduler [CFS]
- Next by Date: [KJ][PATCH] i2c: SPIN_LOCK_UNLOCKED cleanup
- Previous by thread: Re: [PATCH][BUG] Fix possible NULL pointer access in 8250 serial driver
- Next by thread: Re: [PATCH][BUG] Fix possible NULL pointer access in 8250 serial driver
- Index(es):
 |