public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Liu hua <sdu.liu@huawei.com>
To: Nicolas Pitre <nicolas.pitre@linaro.org>,
	Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: <will.deacon@arm.com>, <vitalya@ti.com>, <cyril@ti.com>,
	<santosh.shilimkar@ti.com>, <lauraa@codeaurora.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <wangnan0@huawei.com>,
	<peifeiyue@huawei.com>, <liusdu@126.co>
Subject: Re: [PATCH v3 0/2] change ARM linux memory layout to support 32 CPUs
Date: Sun, 4 May 2014 10:34:38 +0800	[thread overview]
Message-ID: <5365A73E.1060006@huawei.com> (raw)
In-Reply-To: <alpine.LFD.2.11.1404221949510.980@knanqh.ubzr>

On 2014/4/23 7:50, Nicolas Pitre wrote:
> On Tue, 22 Apr 2014, Russell King - ARM Linux wrote:
> 
>> 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@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.
> 
> Indeed.  The stable qualifier should be dropped.
> 
> 
> Nicolas
> 
> .
> 
I am very sorry to ignore this mail for ten days! We have a platform of 16
CPUs, for which these patches are necessary(15CPUs for old memory layout).
But only with these patches, the ARM linux can not run on it.(gic part
should also be changed)

So you are right. It seems to be a new feature. Sorry for this mistake.
If anything I should do, please inform me!

Thanks,
Liu Hua




      reply	other threads:[~2014-05-04  2:37 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 ` [PATCH v3 0/2] change ARM linux memory layout " Russell King - ARM Linux
2014-04-22 23:50   ` Nicolas Pitre
2014-05-04  2:34     ` Liu hua [this message]

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=5365A73E.1060006@huawei.com \
    --to=sdu.liu@huawei.com \
    --cc=cyril@ti.com \
    --cc=lauraa@codeaurora.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=liusdu@126.co \
    --cc=nicolas.pitre@linaro.org \
    --cc=peifeiyue@huawei.com \
    --cc=santosh.shilimkar@ti.com \
    --cc=vitalya@ti.com \
    --cc=wangnan0@huawei.com \
    --cc=will.deacon@arm.com \
    /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