Umm, it's really late to merge things for 2.6.19. How severe is this bug? Why has it not been found until now if it causing crashes? - R. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org 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 2.6.19] ehca: bug fix: use wqe offset instead wqe address to determine pending work requests
- From: Hoang-Nam Nguyen <hnguyen@linux.vnet.ibm.com>
- Re: [PATCH 2.6.19] ehca: bug fix: use wqe offset instead wqe address to determine pending work requests
- References:
- [PATCH 2.6.19] ehca: bug fix: use wqe offset instead wqe address to determine pending work requests
- From: Hoang-Nam Nguyen <hnguyen@linux.vnet.ibm.com>
- [PATCH 2.6.19] ehca: bug fix: use wqe offset instead wqe address to determine pending work requests
- Prev by Date: Re: Problem with DMA on x86_64 with 3 GB RAM
- Next by Date: [PATCH 2.6.19] bonding: incorrect bonding state reported via ioctl
- Previous by thread: [PATCH 2.6.19] ehca: bug fix: use wqe offset instead wqe address to determine pending work requests
- Next by thread: Re: [PATCH 2.6.19] ehca: bug fix: use wqe offset instead wqe address to determine pending work requests
- Index(es):
![]() |