On 18/06/07, Christoph Lameter <[email protected]> wrote:
On Mon, 18 Jun 2007, Michal Piotrowski wrote: > > Does this patch fix the issue? > Unfortunately no. > > AFAIR I didn't see it in 2.6.22-rc4-mm2 Seems that I miscounted. We need a larger safe area.
Still the same. Regards, Michal -- LOG http://www.stardust.webpages.pl/log/ - 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 00/26] Current slab allocator / SLUB patch queue
- From: Christoph Lameter <[email protected]>
- Re: [patch 00/26] Current slab allocator / SLUB patch queue
- References:
- [patch 00/26] Current slab allocator / SLUB patch queue
- From: [email protected]
- Re: [patch 00/26] Current slab allocator / SLUB patch queue
- From: Michal Piotrowski <[email protected]>
- Re: [patch 00/26] Current slab allocator / SLUB patch queue
- From: Christoph Lameter <[email protected]>
- Re: [patch 00/26] Current slab allocator / SLUB patch queue
- From: "Michal Piotrowski" <[email protected]>
- Re: [patch 00/26] Current slab allocator / SLUB patch queue
- From: Christoph Lameter <[email protected]>
- [patch 00/26] Current slab allocator / SLUB patch queue
- Prev by Date: Re: mea culpa on the meaning of Tivoization
- Next by Date: Re: [patch] use __asm__ and __volatile__ in i386/arm/s390 byteorder.h
- Previous by thread: Re: [patch 00/26] Current slab allocator / SLUB patch queue
- Next by thread: Re: [patch 00/26] Current slab allocator / SLUB patch queue
- Index(es):
 |