On Wed, Oct 19, 2005 at 01:56:53PM +0200, Ingo Molnar wrote: > > So, should I resend the patch without the comment? > > i guess so. OTOH, if it was so obvious, why did it stay unfixed for so > long ;-) a) the code is pretty new b) this isn't a serious problem for kernels without your preempt-rt patch - 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:
- scsi_eh / 1394 bug - -rt7
- From: Mark Knecht <[email protected]>
- Re: scsi_eh / 1394 bug - -rt7
- From: Lee Revell <[email protected]>
- Re: scsi_eh / 1394 bug - -rt7
- From: Lee Revell <[email protected]>
- Re: scsi_eh / 1394 bug - -rt7
- From: Steven Rostedt <[email protected]>
- [PATCH] scsi_error thread exits in TASK_INTERRUPTIBLE state.
- From: Steven Rostedt <[email protected]>
- Re: [PATCH] scsi_error thread exits in TASK_INTERRUPTIBLE state.
- From: Christoph Hellwig <[email protected]>
- Re: [PATCH] scsi_error thread exits in TASK_INTERRUPTIBLE state.
- From: Steven Rostedt <[email protected]>
- Re: [PATCH] scsi_error thread exits in TASK_INTERRUPTIBLE state.
- From: Ingo Molnar <[email protected]>
- scsi_eh / 1394 bug - -rt7
- Prev by Date: Re: [PATCH] ktimers subsystem 2.6.14-rc2-kt5
- Next by Date: Re: [patch 2.6.14-rc3 2/3] sundance: probe PHYs from MII address 0
- Previous by thread: Re: [PATCH] scsi_error thread exits in TASK_INTERRUPTIBLE state.
- Next by thread: Re: scsi_eh / 1394 bug - -rt7
- Index(es):
 |