On Wed, 25 Jul 2007 13:55:02 +0100
[EMAIL PROTECTED] (Mel Gorman) wrote:
> > mm/sparse.c: In function `sparse_init':
> > mm/sparse.c:482: error: implicit declaration of function
> > `sparse_early_usemap_alloc'
> > mm/sparse.c:482: warning: assignment makes pointer from integer without a
> > cast
e_early_nid(ms);
> -
> - usemap = alloc_bootmem_node(NODE_DATA(nid), usemap_size());
> - if (usemap)
> - return usemap;
> -
> - printk(KERN_WARNING "%s: allocation failed\n", __FUNCTION__);
> - return NULL;
> -}
> -
> /*
>
On (25/07/07 15:49), Mel Gorman didst pronounce:
> > SuperH allmodconfig blew up:
> >
> > mm/sparse.c: In function `sparse_init':
> > mm/sparse.c:482: error: implicit declaration of function
> > `sparse_early_usemap_alloc'
> > mm/sparse.c:482: warning: assignment makes pointer from integer withou
On (24/07/07 22:01), Andrew Morton didst pronounce:
> On Tue, 13 Mar 2007 10:42:02 + [EMAIL PROTECTED] (Mel Gorman) wrote:
>
> > There are problems in the use of SPARSEMEM and pageblock flags that causes
> > problems on ia64.
> >
> >
>
> SuperH allmodconfig blew up:
>
> mm/sparse.c: In fun
On (24/07/07 22:01), Andrew Morton didst pronounce:
> On Tue, 13 Mar 2007 10:42:02 + [EMAIL PROTECTED] (Mel Gorman) wrote:
>
> > There are problems in the use of SPARSEMEM and pageblock flags that causes
> > problems on ia64.
> >
> > The first part of the problem is that units are incorrect i
On Tue, 13 Mar 2007 10:42:02 + [EMAIL PROTECTED] (Mel Gorman) wrote:
> There are problems in the use of SPARSEMEM and pageblock flags that causes
> problems on ia64.
>
> The first part of the problem is that units are incorrect in
> SECTION_BLOCKFLAGS_BITS computation. This results in a map_s
There are problems in the use of SPARSEMEM and pageblock flags that causes
problems on ia64.
The first part of the problem is that units are incorrect in
SECTION_BLOCKFLAGS_BITS computation. This results in a map_section's
section_mem_map being treated as part of a bitmap which isn't good. This
w
7 matches
Mail list logo