[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20110413084047.41DD.A69D9226@jp.fujitsu.com>
Date: Wed, 13 Apr 2011 08:41:02 +0900 (JST)
From: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
To: Alexey Dobriyan <adobriyan@...il.com>
Cc: kosaki.motohiro@...fujitsu.com,
Andrew Morton <akpm@...ux-foundation.org>,
LKML <linux-kernel@...r.kernel.org>,
linux-mm <linux-mm@...ck.org>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Hugh Dickins <hughd@...gle.com>,
Dave Hansen <dave@...ux.vnet.ibm.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
Paul Mundt <lethal@...ux-sh.org>,
Russell King <linux@....linux.org.uk>
Subject: Re: mm: convert vma->vm_flags to 64bit
> On Tue, Apr 12, 2011 at 10:12 AM, KOSAKI Motohiro
> <kosaki.motohiro@...fujitsu.com> wrote:
> > After next year? All developers don't have to ignore compiler warnings!
>
> At least add vm_flags_t which is sparse-checked, just like we do with gfp_t.
Good idea.
> VM_SAO is ppc64 only, so it could be moved into high part,
> freeing 1 bit?
Sure. But It have to be done after two kernel release cycle or so on.
I mean I'm afraid anyone add new vm_flags usage concurrently.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists