From: thunder.leizhen@huawei.com (Leizhen (ThunderTown))
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 00/14] fix some type infos and bugs for arm64/of numa
Date: Wed, 8 Jun 2016 16:59:03 +0800 [thread overview]
Message-ID: <5757DE57.10700@huawei.com> (raw)
In-Reply-To: <20160607135852.GA20477@arm.com>
On 2016/6/7 21:58, Will Deacon wrote:
> On Tue, Jun 07, 2016 at 04:08:04PM +0800, Zhen Lei wrote:
>> v3 -> v4:
>> 1. Packed three patches of Kefeng Wang, patch6-8.
>> 2. Add 6 new patches(9-15) to enhance the numa on arm64.
>>
>> v2 -> v3:
>> 1. Adjust patch2 and patch5 according to Matthias Brugger's advice, to make the
>> patches looks more well. The final code have no change.
>>
>> v1 -> v2:
>> 1. Base on https://lkml.org/lkml/2016/5/24/679
>
> If you want bug fixes to land in 4.7, you'll need to base them on a
> mainline kernel.
I heared that David Daney's acpi numa patch series was accepted and put into next branch(Linux 4.8).
Otherwise I will suggest him sending his patch6-7 to mainline first. So that, only a very small conflict
will be exist.
I also tested that:
1. git am David Daney's patch6-7, then git am all of my patches on a branch, named branch A.
2. git am David Daney's patch6-7 on another branch, named branch B.
3. when I git merge B into branch A, it's still conflict. So I guess git merge is based on source code, rather than patches.
So at present, unless the maintainers are willing to resolve the conflict, otherwise I update my patches will not work.
Fortunately, these patches are not particularly urgent. So I think I can wait until Linux 4.8 start, then send these patches again.
But I'm not sure whether these patches can be merged into Linux 4.8, I really hope.
>
> Will
>
> .
>
WARNING: multiple messages have this Message-ID (diff)
From: "Leizhen (ThunderTown)" <thunder.leizhen-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
To: Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org>
Cc: Catalin Marinas <catalin.marinas-5wv7dgnIgG8@public.gmane.org>,
linux-arm-kernel
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
Ganapatrao Kulkarni
<gkulkarni-M3mlKVOIwJVv6pq1l3V1OdBPR1lH4CV8@public.gmane.org>,
Robert Richter <rrichter-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org>,
David Daney <david.daney-YGCgFSpz5w/QT0dZR+AlfA@public.gmane.org>,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Frank Rowand
<frowand.list-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Grant Likely
<grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
devicetree <devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-kernel
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Zefan Li <lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>,
Xinwei Hu <huxinwei-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>,
Tianhong Ding
<dingtianhong-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>,
Hanjun Guo <guohanjun-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH v4 00/14] fix some type infos and bugs for arm64/of numa
Date: Wed, 8 Jun 2016 16:59:03 +0800 [thread overview]
Message-ID: <5757DE57.10700@huawei.com> (raw)
In-Reply-To: <20160607135852.GA20477-5wv7dgnIgG8@public.gmane.org>
On 2016/6/7 21:58, Will Deacon wrote:
> On Tue, Jun 07, 2016 at 04:08:04PM +0800, Zhen Lei wrote:
>> v3 -> v4:
>> 1. Packed three patches of Kefeng Wang, patch6-8.
>> 2. Add 6 new patches(9-15) to enhance the numa on arm64.
>>
>> v2 -> v3:
>> 1. Adjust patch2 and patch5 according to Matthias Brugger's advice, to make the
>> patches looks more well. The final code have no change.
>>
>> v1 -> v2:
>> 1. Base on https://lkml.org/lkml/2016/5/24/679
>
> If you want bug fixes to land in 4.7, you'll need to base them on a
> mainline kernel.
I heared that David Daney's acpi numa patch series was accepted and put into next branch(Linux 4.8).
Otherwise I will suggest him sending his patch6-7 to mainline first. So that, only a very small conflict
will be exist.
I also tested that:
1. git am David Daney's patch6-7, then git am all of my patches on a branch, named branch A.
2. git am David Daney's patch6-7 on another branch, named branch B.
3. when I git merge B into branch A, it's still conflict. So I guess git merge is based on source code, rather than patches.
So at present, unless the maintainers are willing to resolve the conflict, otherwise I update my patches will not work.
Fortunately, these patches are not particularly urgent. So I think I can wait until Linux 4.8 start, then send these patches again.
But I'm not sure whether these patches can be merged into Linux 4.8, I really hope.
>
> Will
>
> .
>
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: "Leizhen (ThunderTown)" <thunder.leizhen@huawei.com>
To: Will Deacon <will.deacon@arm.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Ganapatrao Kulkarni <gkulkarni@caviumnetworks.com>,
Robert Richter <rrichter@cavium.com>,
"David Daney" <david.daney@cavium.com>,
Rob Herring <robh+dt@kernel.org>,
"Frank Rowand" <frowand.list@gmail.com>,
Grant Likely <grant.likely@linaro.org>,
devicetree <devicetree@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Zefan Li <lizefan@huawei.com>, Xinwei Hu <huxinwei@huawei.com>,
Tianhong Ding <dingtianhong@huawei.com>,
Hanjun Guo <guohanjun@huawei.com>
Subject: Re: [PATCH v4 00/14] fix some type infos and bugs for arm64/of numa
Date: Wed, 8 Jun 2016 16:59:03 +0800 [thread overview]
Message-ID: <5757DE57.10700@huawei.com> (raw)
In-Reply-To: <20160607135852.GA20477@arm.com>
On 2016/6/7 21:58, Will Deacon wrote:
> On Tue, Jun 07, 2016 at 04:08:04PM +0800, Zhen Lei wrote:
>> v3 -> v4:
>> 1. Packed three patches of Kefeng Wang, patch6-8.
>> 2. Add 6 new patches(9-15) to enhance the numa on arm64.
>>
>> v2 -> v3:
>> 1. Adjust patch2 and patch5 according to Matthias Brugger's advice, to make the
>> patches looks more well. The final code have no change.
>>
>> v1 -> v2:
>> 1. Base on https://lkml.org/lkml/2016/5/24/679
>
> If you want bug fixes to land in 4.7, you'll need to base them on a
> mainline kernel.
I heared that David Daney's acpi numa patch series was accepted and put into next branch(Linux 4.8).
Otherwise I will suggest him sending his patch6-7 to mainline first. So that, only a very small conflict
will be exist.
I also tested that:
1. git am David Daney's patch6-7, then git am all of my patches on a branch, named branch A.
2. git am David Daney's patch6-7 on another branch, named branch B.
3. when I git merge B into branch A, it's still conflict. So I guess git merge is based on source code, rather than patches.
So at present, unless the maintainers are willing to resolve the conflict, otherwise I update my patches will not work.
Fortunately, these patches are not particularly urgent. So I think I can wait until Linux 4.8 start, then send these patches again.
But I'm not sure whether these patches can be merged into Linux 4.8, I really hope.
>
> Will
>
> .
>
next prev parent reply other threads:[~2016-06-08 8:59 UTC|newest]
Thread overview: 91+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 8:08 [PATCH v4 00/14] fix some type infos and bugs for arm64/of numa Zhen Lei
2016-06-07 8:08 ` Zhen Lei
2016-06-07 8:08 ` Zhen Lei
2016-06-07 8:08 ` [PATCH v4 01/14] of/numa: remove a duplicated pr_debug information Zhen Lei
2016-06-07 8:08 ` Zhen Lei
2016-06-07 8:08 ` Zhen Lei
2016-06-07 8:08 ` [PATCH v4 02/14] of/numa: fix a memory@ node can only contains one memory block Zhen Lei
2016-06-07 8:08 ` Zhen Lei
2016-06-07 8:08 ` Zhen Lei
2016-06-07 8:08 ` [PATCH v4 03/14] arm64/numa: add nid check for " Zhen Lei
2016-06-07 8:08 ` Zhen Lei
2016-06-07 8:08 ` Zhen Lei
2016-06-07 8:08 ` [PATCH v4 04/14] of/numa: remove a duplicated warning Zhen Lei
2016-06-07 8:08 ` Zhen Lei
2016-06-07 8:08 ` Zhen Lei
2016-06-07 8:08 ` [PATCH v4 05/14] arm64/numa: avoid inconsistent information to be printed Zhen Lei
2016-06-07 8:08 ` Zhen Lei
2016-06-07 8:08 ` Zhen Lei
2016-06-07 8:08 ` [PATCH v4 06/14] of_numa: Use of_get_next_parent to simplify code Zhen Lei
2016-06-07 8:08 ` Zhen Lei
2016-06-07 8:08 ` Zhen Lei
2016-06-07 8:08 ` [PATCH v4 07/14] of_numa: Use pr_fmt() Zhen Lei
2016-06-07 8:08 ` Zhen Lei
2016-06-07 8:08 ` Zhen Lei
2016-06-07 8:08 ` [PATCH v4 08/14] arm64: numa: " Zhen Lei
2016-06-07 8:08 ` Zhen Lei
2016-06-07 8:08 ` Zhen Lei
2016-06-07 8:08 ` [PATCH v4 09/14] arm64/numa: support HAVE_SETUP_PER_CPU_AREA Zhen Lei
2016-06-07 8:08 ` Zhen Lei
2016-06-07 8:08 ` Zhen Lei
2016-06-07 8:08 ` [PATCH v4 10/14] arm64/numa: define numa_distance as array to simplify code Zhen Lei
2016-06-07 8:08 ` Zhen Lei
2016-06-07 8:08 ` Zhen Lei
2016-06-07 8:08 ` [PATCH v4 11/14] arm64/numa: support HAVE_MEMORYLESS_NODES Zhen Lei
2016-06-07 8:08 ` Zhen Lei
2016-06-07 8:08 ` Zhen Lei
2016-06-07 8:31 ` Ganapatrao Kulkarni
2016-06-07 8:31 ` Ganapatrao Kulkarni
2016-06-07 8:31 ` Ganapatrao Kulkarni
2016-06-07 12:57 ` Leizhen (ThunderTown)
2016-06-07 12:57 ` Leizhen (ThunderTown)
2016-06-07 14:01 ` Ganapatrao Kulkarni
2016-06-07 14:01 ` Ganapatrao Kulkarni
2016-06-08 2:16 ` Leizhen (ThunderTown)
2016-06-08 2:16 ` Leizhen (ThunderTown)
2016-06-08 2:16 ` Leizhen (ThunderTown)
2016-06-08 4:45 ` Ganapatrao Kulkarni
2016-06-08 4:45 ` Ganapatrao Kulkarni
2016-06-08 7:49 ` Leizhen (ThunderTown)
2016-06-08 7:49 ` Leizhen (ThunderTown)
2016-06-08 7:49 ` Leizhen (ThunderTown)
2016-06-07 8:08 ` [PATCH v4 12/14] arm64/numa: remove some useless code Zhen Lei
2016-06-07 8:08 ` Zhen Lei
2016-06-07 8:08 ` Zhen Lei
2016-06-07 8:28 ` Ganapatrao Kulkarni
2016-06-07 8:28 ` Ganapatrao Kulkarni
2016-06-07 12:42 ` Leizhen (ThunderTown)
2016-06-07 12:42 ` Leizhen (ThunderTown)
2016-06-07 8:08 ` [PATCH v4 13/14] of/numa: remove the constraint on the distances of node pairs Zhen Lei
2016-06-07 8:08 ` Zhen Lei
2016-06-07 8:08 ` Zhen Lei
2016-06-07 8:08 ` [PATCH v4 14/14] Documentation: " Zhen Lei
2016-06-07 8:08 ` Zhen Lei
2016-06-07 8:08 ` Zhen Lei
2016-06-10 13:08 ` Rob Herring
2016-06-10 13:08 ` Rob Herring
2016-06-10 13:08 ` Rob Herring
2016-06-07 13:58 ` [PATCH v4 00/14] fix some type infos and bugs for arm64/of numa Will Deacon
2016-06-07 13:58 ` Will Deacon
2016-06-08 8:59 ` Leizhen (ThunderTown) [this message]
2016-06-08 8:59 ` Leizhen (ThunderTown)
2016-06-08 8:59 ` Leizhen (ThunderTown)
2016-06-14 14:22 ` Catalin Marinas
2016-06-14 14:22 ` Catalin Marinas
2016-06-20 6:39 ` Leizhen (ThunderTown)
2016-06-20 6:39 ` Leizhen (ThunderTown)
2016-06-20 6:39 ` Leizhen (ThunderTown)
2016-06-22 1:55 ` Leizhen (ThunderTown)
2016-06-22 1:55 ` Leizhen (ThunderTown)
2016-06-22 1:55 ` Leizhen (ThunderTown)
2016-06-12 7:09 ` Hanjun Guo
2016-06-12 7:09 ` Hanjun Guo
2016-06-12 7:09 ` Hanjun Guo
2016-06-13 10:12 ` Will Deacon
2016-06-13 10:12 ` Will Deacon
2016-06-13 10:12 ` Will Deacon
2016-06-14 10:10 ` Hanjun Guo
2016-06-14 10:10 ` Hanjun Guo
2016-06-14 10:10 ` Hanjun Guo
2016-06-07 20:38 ` Rob Herring
2016-06-07 20:38 ` Rob Herring
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=5757DE57.10700@huawei.com \
--to=thunder.leizhen@huawei.com \
--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 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.