From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/2] change ARM linux memory layout to support 32 CPUs
Date: Tue, 22 Apr 2014 22:31:14 +0100 [thread overview]
Message-ID: <20140422213114.GA24070@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1397559967-26050-1-git-send-email-sdu.liu@huawei.com>
On Tue, Apr 15, 2014 at 07:06:05PM +0800, Liu Hua wrote:
> This patch series change fixmap mapping region to suppport 32 CPUs.
> Because the "top_pmd" covers 0xfffe0000 - 0xffffffff(2M). And part
> is used by vector table. So I move this region down to 0xffc00000
> - 0xffdffff.
Can you explain why you have submitted these patches to my patch tracker
with a copy to stable at vger.kernel.org ?
What makes these qualify for stable tree inclusion? What regression are
they fixing?
We don't put patches into the stable tree for things that /never/ worked
in the past. We've never supported 32 CPUs so I don't think these
qualify.
--
FTTC broadband for 0.8mile line: now at 9.7Mbps down 460kbps up... slowly
improving, and getting towards what was expected from it.
next prev parent reply other threads:[~2014-04-22 21:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 11:06 [PATCH v3 0/2] change ARM linux memory layout to support 32 CPUs Liu Hua
2014-04-15 11:06 ` [PATCH v3 1/2] ARM : fixmap : remove FIX_KMAP_BEGIN and FIX_KMAP_END Liu Hua
2014-04-15 11:06 ` [PATCH v3 2/2] ARM : change fixmap mapping region to support 32 CPUs Liu Hua
2014-04-15 15:06 ` Nicolas Pitre
2014-05-30 15:33 ` Rob Herring
2014-05-30 18:02 ` Will Deacon
2014-05-30 19:25 ` Nicolas Pitre
2014-06-10 6:52 ` Liu hua
2014-08-06 2:51 ` Kees Cook
2014-08-06 3:11 ` Nicolas Pitre
2014-08-06 3:40 ` Liu hua
2014-08-06 16:37 ` Kees Cook
2014-08-06 17:21 ` Nicolas Pitre
2014-08-06 17:28 ` Kees Cook
2014-08-06 22:16 ` Russell King - ARM Linux
2014-08-06 23:22 ` Kees Cook
2014-04-22 21:31 ` Russell King - ARM Linux [this message]
2014-04-22 23:50 ` [PATCH v3 0/2] change ARM linux memory layout " Nicolas Pitre
2014-05-04 2:34 ` Liu hua
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=20140422213114.GA24070@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).