From: Dave Hansen <haveblue@us.ibm.com>
To: Haavard Skinnemoen <hskinnemoen@gmail.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-ia64@vger.kernel.org
Subject: Re: [RFC][PATCH 2/9] conditionally define generic get_order()
Date: Thu, 31 Aug 2006 19:51:23 +0000 [thread overview]
Message-ID: <1157053883.28577.19.camel@localhost.localdomain> (raw)
In-Reply-To: <1defaf580608311141j39aa87e5ldf80db1db54b2edf@mail.gmail.com>
On Thu, 2006-08-31 at 20:41 +0200, Haavard Skinnemoen wrote:
> On 8/31/06, Dave Hansen <haveblue@us.ibm.com> wrote:
> > diff -puN mm/Kconfig~generic-get_order mm/Kconfig
> > --- threadalloc/mm/Kconfig~generic-get_order 2006-08-30 15:14:56.000000000 -0700
> > +++ threadalloc-dave/mm/Kconfig 2006-08-30 15:15:00.000000000 -0700
> > @@ -1,3 +1,7 @@
> > +config ARCH_HAVE_GET_ORDER
> > + def_bool y
> > + depends on IA64 || PPC32 || XTENSA
> > +
>
> I have a feeling this has been discussed before, but wouldn't it be
> better to let each architecture define this in its own Kconfig?
As long as the conditions are simple, I think it would be nice to keep
it this way. It makes it pretty obvious to tell what is going on from
_one_ place.
> At some point, I have to add AVR32 to that list, and if one or more
> other architectures need to do the same, there will be rejects.
True, there will be rejects. But, do you think they will actually take
more than a moment to merge?
-- Dave
WARNING: multiple messages have this Message-ID (diff)
From: Dave Hansen <haveblue@us.ibm.com>
To: Haavard Skinnemoen <hskinnemoen@gmail.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-ia64@vger.kernel.org
Subject: Re: [RFC][PATCH 2/9] conditionally define generic get_order() (ARCH_HAS_GET_ORDER)
Date: Thu, 31 Aug 2006 12:51:23 -0700 [thread overview]
Message-ID: <1157053883.28577.19.camel@localhost.localdomain> (raw)
In-Reply-To: <1defaf580608311141j39aa87e5ldf80db1db54b2edf@mail.gmail.com>
On Thu, 2006-08-31 at 20:41 +0200, Haavard Skinnemoen wrote:
> On 8/31/06, Dave Hansen <haveblue@us.ibm.com> wrote:
> > diff -puN mm/Kconfig~generic-get_order mm/Kconfig
> > --- threadalloc/mm/Kconfig~generic-get_order 2006-08-30 15:14:56.000000000 -0700
> > +++ threadalloc-dave/mm/Kconfig 2006-08-30 15:15:00.000000000 -0700
> > @@ -1,3 +1,7 @@
> > +config ARCH_HAVE_GET_ORDER
> > + def_bool y
> > + depends on IA64 || PPC32 || XTENSA
> > +
>
> I have a feeling this has been discussed before, but wouldn't it be
> better to let each architecture define this in its own Kconfig?
As long as the conditions are simple, I think it would be nice to keep
it this way. It makes it pretty obvious to tell what is going on from
_one_ place.
> At some point, I have to add AVR32 to that list, and if one or more
> other architectures need to do the same, there will be rejects.
True, there will be rejects. But, do you think they will actually take
more than a moment to merge?
-- Dave
WARNING: multiple messages have this Message-ID (diff)
From: Dave Hansen <haveblue@us.ibm.com>
To: Haavard Skinnemoen <hskinnemoen@gmail.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-ia64@vger.kernel.org
Subject: Re: [RFC][PATCH 2/9] conditionally define generic get_order() (ARCH_HAS_GET_ORDER)
Date: Thu, 31 Aug 2006 12:51:23 -0700 [thread overview]
Message-ID: <1157053883.28577.19.camel@localhost.localdomain> (raw)
In-Reply-To: <1defaf580608311141j39aa87e5ldf80db1db54b2edf@mail.gmail.com>
On Thu, 2006-08-31 at 20:41 +0200, Haavard Skinnemoen wrote:
> On 8/31/06, Dave Hansen <haveblue@us.ibm.com> wrote:
> > diff -puN mm/Kconfig~generic-get_order mm/Kconfig
> > --- threadalloc/mm/Kconfig~generic-get_order 2006-08-30 15:14:56.000000000 -0700
> > +++ threadalloc-dave/mm/Kconfig 2006-08-30 15:15:00.000000000 -0700
> > @@ -1,3 +1,7 @@
> > +config ARCH_HAVE_GET_ORDER
> > + def_bool y
> > + depends on IA64 || PPC32 || XTENSA
> > +
>
> I have a feeling this has been discussed before, but wouldn't it be
> better to let each architecture define this in its own Kconfig?
As long as the conditions are simple, I think it would be nice to keep
it this way. It makes it pretty obvious to tell what is going on from
_one_ place.
> At some point, I have to add AVR32 to that list, and if one or more
> other architectures need to do the same, there will be rejects.
True, there will be rejects. But, do you think they will actually take
more than a moment to merge?
-- Dave
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2006-08-31 19:51 UTC|newest]
Thread overview: 80+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-30 22:16 [RFC][PATCH 0/9] generic PAGE_SIZE infrastructure (v4) Dave Hansen
2006-08-30 22:16 ` Dave Hansen
2006-08-30 22:16 ` Dave Hansen
2006-08-30 22:16 ` [RFC][PATCH 1/9] put alignment macros in align.h Dave Hansen
2006-08-30 22:16 ` Dave Hansen
2006-08-30 22:16 ` Dave Hansen
2006-08-30 22:16 ` [RFC][PATCH 2/9] conditionally define generic get_order() (ARCH_HAS_GET_ORDER) Dave Hansen
2006-08-30 22:16 ` Dave Hansen
2006-08-30 22:16 ` Dave Hansen
2006-08-31 18:41 ` Haavard Skinnemoen
2006-08-31 18:41 ` Haavard Skinnemoen
2006-08-31 18:41 ` Haavard Skinnemoen
2006-08-31 19:51 ` Dave Hansen [this message]
2006-08-31 19:51 ` Dave Hansen
2006-08-31 19:51 ` Dave Hansen
2006-08-30 22:16 ` [RFC][PATCH 3/9] actual generic PAGE_SIZE infrastructure Dave Hansen
2006-08-30 22:16 ` Dave Hansen
2006-08-30 22:16 ` Dave Hansen
2006-08-31 0:08 ` Christoph Lameter
2006-08-31 0:08 ` Christoph Lameter
2006-08-31 0:08 ` Christoph Lameter
2006-08-31 17:57 ` Dave Hansen
2006-08-31 17:57 ` Dave Hansen
2006-08-31 17:57 ` Dave Hansen
2006-08-31 18:06 ` Christoph Lameter
2006-08-31 18:06 ` Christoph Lameter
2006-08-31 18:06 ` Christoph Lameter
2006-08-31 20:50 ` Dave Hansen
2006-08-31 20:50 ` Dave Hansen
2006-08-31 20:50 ` Dave Hansen
2006-09-05 11:20 ` Martin Waitz
2006-09-05 11:20 ` Martin Waitz
2006-09-05 16:47 ` Dave Hansen
2006-09-05 16:47 ` Dave Hansen
2006-09-05 16:47 ` Dave Hansen
2006-10-17 7:29 ` Qi Yong
2006-10-17 7:29 ` Qi Yong
2006-10-17 7:29 ` Qi Yong
2006-08-30 22:16 ` [RFC][PATCH 4/9] ia64 generic PAGE_SIZE Dave Hansen
2006-08-30 22:16 ` Dave Hansen
2006-08-30 22:16 ` Dave Hansen
2006-08-30 23:57 ` Christoph Lameter
2006-08-30 23:57 ` Christoph Lameter
2006-08-30 23:57 ` Christoph Lameter
2006-08-31 17:38 ` Dave Hansen
2006-08-31 17:38 ` Dave Hansen
2006-08-31 17:38 ` Dave Hansen
2006-08-31 17:39 ` Christoph Lameter
2006-08-31 17:39 ` Christoph Lameter
2006-08-31 17:39 ` Christoph Lameter
2006-08-30 22:16 ` [RFC][PATCH 6/9] mips " Dave Hansen
2006-08-30 22:16 ` Dave Hansen
2006-08-30 22:16 ` Dave Hansen
2006-08-30 22:16 ` [RFC][PATCH 5/9] sparc64 " Dave Hansen
2006-08-30 22:16 ` Dave Hansen
2006-08-30 22:16 ` Dave Hansen
2006-08-30 22:27 ` David Miller
2006-08-30 22:27 ` David Miller, Dave Hansen
2006-08-30 22:27 ` David Miller
2006-08-30 22:16 ` [RFC][PATCH 7/9] parisc " Dave Hansen
2006-08-30 22:16 ` Dave Hansen
2006-08-30 22:16 ` Dave Hansen
2006-08-30 22:40 ` Kyle McMartin
2006-08-30 22:40 ` Kyle McMartin
2006-08-30 22:40 ` Kyle McMartin
2006-08-30 22:48 ` Dave Hansen
2006-08-30 22:48 ` Dave Hansen
2006-08-30 22:48 ` Dave Hansen
2006-08-30 22:16 ` [RFC][PATCH 8/9] powerpc " Dave Hansen
2006-08-30 22:16 ` Dave Hansen
2006-08-30 22:16 ` Dave Hansen
2006-08-30 22:16 ` [RFC][PATCH 9/9] convert the "easy" architectures to " Dave Hansen
2006-08-30 22:16 ` Dave Hansen
2006-08-30 22:16 ` Dave Hansen
2006-08-31 0:33 ` [RFC][PATCH 0/9] generic PAGE_SIZE infrastructure (v4) Paul Mackerras
2006-08-31 0:33 ` Paul Mackerras
2006-08-31 0:33 ` Paul Mackerras
2006-08-31 21:03 ` Dave Hansen
2006-08-31 21:03 ` Dave Hansen
2006-08-31 21:03 ` Dave Hansen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1157053883.28577.19.camel@localhost.localdomain \
--to=haveblue@us.ibm.com \
--cc=hskinnemoen@gmail.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.