mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Li.Xiubo@freescale.com" <Li.Xiubo@freescale.com>
To: "linux@arm.linux.org.uk" <linux@arm.linux.org.uk>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>
Subject: RE: [PATCH] ARM: Kconfig: Open force maximum zone order for all SoCs
Date: Fri, 26 Sep 2014 05:30:40 +0000	[thread overview]
Message-ID: <9dc024498c904d48b3a25430f8d31f29@BY2PR0301MB0613.namprd03.prod.outlook.com> (raw)
In-Reply-To: <1409546541-4129-1-git-send-email-Li.Xiubo@freescale.com>

Hi Russell,

I'd like to know the status of this patch.

Our Platforms depend on it.

Thanks,

BRs
Xiubo

> -----Original Message-----
> From: Xiubo Li [mailto:Li.Xiubo@freescale.com]
> Sent: Monday, September 01, 2014 12:42 PM
> To: linux@arm.linux.org.uk; linux-arm-kernel@lists.infradead.org
> Cc: linux-kernel@vger.kernel.org; Xiubo Li-B47053
> Subject: [PATCH] ARM: Kconfig: Open force maximum zone order for all SoCs
> 
> Signed-off-by: Xiubo Li <Li.Xiubo@freescale.com>
> ---
>  arch/arm/Kconfig | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
> index c49a775..bf8445c 100644
> --- a/arch/arm/Kconfig
> +++ b/arch/arm/Kconfig
> @@ -1687,7 +1687,7 @@ config ARCH_WANT_GENERAL_HUGETLB
>  source "mm/Kconfig"
> 
>  config FORCE_MAX_ZONEORDER
> -	int "Maximum zone order" if ARCH_SHMOBILE_LEGACY
> +	int "Maximum zone order"
>  	range 11 64 if ARCH_SHMOBILE_LEGACY
>  	default "12" if SOC_AM33XX
>  	default "9" if SA1111 || ARCH_EFM32
> --
> 1.8.4


  reply	other threads:[~2014-09-26  5:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-01  4:42 Xiubo Li
2014-09-26  5:30 ` Li.Xiubo [this message]
2014-09-26  8:20   ` Russell King - ARM Linux
2014-09-26  8:39     ` Li.Xiubo
2014-09-26  8:44       ` Russell King - ARM Linux
2014-09-26  8:46         ` Li.Xiubo

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=9dc024498c904d48b3a25430f8d31f29@BY2PR0301MB0613.namprd03.prod.outlook.com \
    --to=li.xiubo@freescale.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®