From: Michael Ellerman <mpe@ellerman.id.au>
To: Christophe Leroy <christophe.leroy@c-s.fr>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 2/4] powerpc/mm: Move book3s64 specifics in subdirectory mm/book3s64
Date: Thu, 02 May 2019 17:11:40 +1000 [thread overview]
Message-ID: <87sgtx5o0j.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <c4afde657ef9e4ad0266ae62e9907313c41c4a16.1553853405.git.christophe.leroy@c-s.fr>
Christophe Leroy <christophe.leroy@c-s.fr> writes:
> Many files in arch/powerpc/mm are only for book3S64. This patch
> creates a subdirectory for them.
>
> Signed-off-by: Christophe Leroy <christophe.leroy@c-s.fr>
> ---
> arch/powerpc/mm/Makefile | 25 +++----------------
> arch/powerpc/mm/book3s64/Makefile | 28 ++++++++++++++++++++++
> arch/powerpc/mm/{ => book3s64}/hash64_4k.c | 0
> arch/powerpc/mm/{ => book3s64}/hash64_64k.c | 0
> arch/powerpc/mm/{ => book3s64}/hash_native_64.c | 0
> arch/powerpc/mm/{ => book3s64}/hash_utils_64.c | 0
> arch/powerpc/mm/{ => book3s64}/hugepage-hash64.c | 0
> .../powerpc/mm/{ => book3s64}/hugetlbpage-hash64.c | 0
> arch/powerpc/mm/{ => book3s64}/hugetlbpage-radix.c | 0
> .../mm/{ => book3s64}/mmu_context_book3s64.c | 0
> arch/powerpc/mm/{ => book3s64}/mmu_context_iommu.c | 0
> arch/powerpc/mm/{ => book3s64}/pgtable-book3s64.c | 0
> arch/powerpc/mm/{ => book3s64}/pgtable-hash64.c | 0
> arch/powerpc/mm/{ => book3s64}/pgtable-radix.c | 0
> arch/powerpc/mm/{ => book3s64}/pkeys.c | 0
> arch/powerpc/mm/{ => book3s64}/slb.c | 0
> arch/powerpc/mm/{ => book3s64}/subpage-prot.c | 0
> arch/powerpc/mm/{ => book3s64}/tlb-radix.c | 0
> arch/powerpc/mm/{ => book3s64}/tlb_hash64.c | 0
> arch/powerpc/mm/{ => book3s64}/vphn.c | 0
> arch/powerpc/mm/{ => book3s64}/vphn.h | 0
> arch/powerpc/mm/numa.c | 2 +-
> 22 files changed, 32 insertions(+), 23 deletions(-)
> create mode 100644 arch/powerpc/mm/book3s64/Makefile
> rename arch/powerpc/mm/{ => book3s64}/hash64_4k.c (100%)
> rename arch/powerpc/mm/{ => book3s64}/hash64_64k.c (100%)
> rename arch/powerpc/mm/{ => book3s64}/hash_native_64.c (100%)
> rename arch/powerpc/mm/{ => book3s64}/hash_utils_64.c (100%)
> rename arch/powerpc/mm/{ => book3s64}/hugepage-hash64.c (100%)
> rename arch/powerpc/mm/{ => book3s64}/hugetlbpage-hash64.c (100%)
> rename arch/powerpc/mm/{ => book3s64}/hugetlbpage-radix.c (100%)
> rename arch/powerpc/mm/{ => book3s64}/mmu_context_book3s64.c (100%)
> rename arch/powerpc/mm/{ => book3s64}/mmu_context_iommu.c (100%)
> rename arch/powerpc/mm/{ => book3s64}/pgtable-book3s64.c (100%)
> rename arch/powerpc/mm/{ => book3s64}/pgtable-hash64.c (100%)
> rename arch/powerpc/mm/{ => book3s64}/pgtable-radix.c (100%)
> rename arch/powerpc/mm/{ => book3s64}/pkeys.c (100%)
> rename arch/powerpc/mm/{ => book3s64}/slb.c (100%)
> rename arch/powerpc/mm/{ => book3s64}/subpage-prot.c (100%)
> rename arch/powerpc/mm/{ => book3s64}/tlb-radix.c (100%)
> rename arch/powerpc/mm/{ => book3s64}/tlb_hash64.c (100%)
Do you mind if I take this but rework the destination names in the process?
I don't like having eg. book3s64/pgtable-book3s64.c
And some of the other names could use a bit of cleanup too.
What about:
arch/powerpc/mm/{hash64_4k.c => book3s64/hash_4k.c}
arch/powerpc/mm/{hash64_64k.c => book3s64/hash_64k.c}
arch/powerpc/mm/{hugepage-hash64.c => book3s64/hash_hugepage.c}
arch/powerpc/mm/{hugetlbpage-hash64.c => book3s64/hash_hugetlbpage.c}
arch/powerpc/mm/{hash_native_64.c => book3s64/hash_native.c}
arch/powerpc/mm/{pgtable-hash64.c => book3s64/hash_pgtable.c}
arch/powerpc/mm/{tlb_hash64.c => book3s64/hash_tlb.c}
arch/powerpc/mm/{hash_utils_64.c => book3s64/hash_utils.c}
arch/powerpc/mm/{mmu_context_iommu.c => book3s64/iommu_api.c}
arch/powerpc/mm/{mmu_context_book3s64.c => book3s64/mmu_context.c}
arch/powerpc/mm/{pgtable-book3s64.c => book3s64/pgtable.c}
arch/powerpc/mm/{hugetlbpage-radix.c => book3s64/radix_hugetlbpage.c}
arch/powerpc/mm/{pgtable-radix.c => book3s64/radix_pgtable.c}
arch/powerpc/mm/{tlb-radix.c => book3s64/radix_tlb.c}
cheers
next prev parent reply other threads:[~2019-05-02 7:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-29 9:59 [PATCH v1 0/4] powerpc: Split arch/powerpc/mm/ directory Christophe Leroy
2019-03-29 9:59 ` [PATCH v1 1/4] powerpc/mm: change #include "mmu_decl.h" to <mm/mmu_decl.h> Christophe Leroy
2019-05-03 6:59 ` Michael Ellerman
2019-03-29 10:00 ` [PATCH v1 2/4] powerpc/mm: Move book3s64 specifics in subdirectory mm/book3s64 Christophe Leroy
2019-05-02 7:11 ` Michael Ellerman [this message]
2019-05-02 7:15 ` Christophe Leroy
2019-05-02 11:14 ` Michael Ellerman
2019-03-29 10:00 ` [PATCH v1 3/4] powerpc/mm: Move book3s32 " Christophe Leroy
2019-05-02 11:32 ` Michael Ellerman
2019-05-02 11:43 ` Christophe Leroy
2019-03-29 10:00 ` [PATCH v1 4/4] powerpc/mm: Move nohash specifics in subdirectory mm/nohash Christophe Leroy
2019-05-02 11:38 ` Michael Ellerman
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=87sgtx5o0j.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=benh@kernel.crashing.org \
--cc=christophe.leroy@c-s.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.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).