From: Catalin Marinas <catalin.marinas@arm.com>
To: Vadym Kochan <vadym.kochan@plvision.eu>
Cc: Will Deacon <will@kernel.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: Kconfig: allow to change FORCE_MAX_ZONEORDER via custom config
Date: Fri, 13 Mar 2020 12:37:41 +0000 [thread overview]
Message-ID: <20200313123741.GC3857972@arrakis.emea.arm.com> (raw)
In-Reply-To: <20200312235037.26072-1-vadym.kochan@plvision.eu>
On Fri, Mar 13, 2020 at 01:50:37AM +0200, Vadym Kochan wrote:
> Add missing config option name which allows to change it via custom
> config.
Why? What is your use-case?
--
Catalin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Catalin Marinas <catalin.marinas@arm.com>
To: Vadym Kochan <vadym.kochan@plvision.eu>
Cc: Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: Kconfig: allow to change FORCE_MAX_ZONEORDER via custom config
Date: Fri, 13 Mar 2020 12:37:41 +0000 [thread overview]
Message-ID: <20200313123741.GC3857972@arrakis.emea.arm.com> (raw)
In-Reply-To: <20200312235037.26072-1-vadym.kochan@plvision.eu>
On Fri, Mar 13, 2020 at 01:50:37AM +0200, Vadym Kochan wrote:
> Add missing config option name which allows to change it via custom
> config.
Why? What is your use-case?
--
Catalin
next prev parent reply other threads:[~2020-03-13 12:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-12 23:50 [PATCH] arm64: Kconfig: allow to change FORCE_MAX_ZONEORDER via custom config Vadym Kochan
2020-03-12 23:50 ` Vadym Kochan
2020-03-13 12:37 ` Catalin Marinas [this message]
2020-03-13 12:37 ` Catalin Marinas
2020-03-13 12:45 ` Vadym Kochan
2020-03-13 12:45 ` Vadym Kochan
2020-03-16 17:42 ` Catalin Marinas
2020-03-16 17:42 ` Catalin Marinas
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=20200313123741.GC3857972@arrakis.emea.arm.com \
--to=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vadym.kochan@plvision.eu \
--cc=will@kernel.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.