From: Michael Ellerman <patch-notifications@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 1/5] powerpc/mm: define empty update_mmu_cache() as static inline
Date: Thu, 22 Aug 2019 23:09:07 +1000 (AEST) [thread overview]
Message-ID: <46DlGs1HPYz9sNk@ozlabs.org> (raw)
In-Reply-To: <668aba4db6b9af6d8a151174e11a4289f1a6bbcd.1565933217.git.christophe.leroy@c-s.fr>
On Fri, 2019-08-16 at 05:41:40 UTC, Christophe Leroy wrote:
> Only BOOK3S and FSL_BOOK3E have a usefull update_mmu_cache().
>
> For the others, just define it static inline.
>
> In the meantime, simplify the FSL_BOOK3E related ifdef as
> book3e_hugetlb_preload() only exists when CONFIG_PPC_FSL_BOOK3E
> is selected.
>
> Signed-off-by: Christophe Leroy <christophe.leroy@c-s.fr>
Series applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/d9642117914c9d3f800b3bacc19d7e388b04edb4
cheers
prev parent reply other threads:[~2019-08-22 13:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-16 5:41 [PATCH 1/5] powerpc/mm: define empty update_mmu_cache() as static inline Christophe Leroy
2019-08-16 5:41 ` [PATCH 2/5] powerpc/mm: move FSL_BOOK3 version of update_mmu_cache() Christophe Leroy
2019-08-16 5:41 ` [PATCH 3/5] powerpc/mm: move update_mmu_cache() into book3s hash utils Christophe Leroy
2019-08-16 5:41 ` [PATCH 4/5] powerpc/mm: Simplify update_mmu_cache() on BOOK3S32 Christophe Leroy
2019-08-16 5:41 ` [PATCH 5/5] powerpc/mm: ppc 603 doesn't need update_mmu_cache() Christophe Leroy
2019-08-22 13:09 ` Michael Ellerman [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=46DlGs1HPYz9sNk@ozlabs.org \
--to=patch-notifications@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).