Date: Mon, 31 Oct 2005 15:11:21 -0800
From: Matt Mackall <mpm@selenic.com>
To: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org,
       linux-arch@vger.kernel.org
Subject: Re: [PATCH 17/20] inflate: mark some arrays as initdata
Message-ID: <20051031231120.GF4367@waste.org>
References: <17.196662837@selenic.com> <18.196662837@selenic.com> <20051031224301.GF20452@flint.arm.linux.org.uk> <20051031225746.GD4367@waste.org> <20051031231052.GA1710@flint.arm.linux.org.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20051031231052.GA1710@flint.arm.linux.org.uk>
User-Agent: Mutt/1.5.9i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 825
Lines: 22

On Mon, Oct 31, 2005 at 11:10:52PM +0000, Russell King wrote:
> That's what threading is for. 8)

What's what's threading is for?

> > I think for ARM, we can simply do -DINITDATA=const, yes?
> 
> No, unless you want to make this const:
> 
> -static u8 window[0x8000]; /* use a statically allocated window */
> +static u8 INITDATA window[0x8000]; /* use a statically allocated window */

Ok, that bit can just be dropped. It needn't be INITDATA anyway, as it
now gets kmalloc'ed for users in the kernel proper. Anything else?

-- 
Mathematics is the supreme nostalgia of our time.
-
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/