[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180418113816.sgxdnxrbg4imzxfx@lakrids.cambridge.arm.com>
Date: Wed, 18 Apr 2018 12:38:16 +0100
From: Mark Rutland <mark.rutland@....com>
To: Arnd Bergmann <arnd@...db.de>
Cc: Linux ARM <linux-arm-kernel@...ts.infradead.org>,
Catalin Marinas <catalin.marinas@....com>, cdall@...nel.org,
drjones@...hat.com, kvmarm@...ts.cs.columbia.edu,
linux-arch <linux-arch@...r.kernel.org>,
Marc Zyngier <marc.zyngier@....com>,
Ramana Radhakrishnan <ramana.radhakrishnan@....com>,
Suzuki K Poulose <suzuki.poulose@....com>,
Will Deacon <will.deacon@....com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Adam Wallis <awallis@...eaurora.org>,
Kernel Hardening <kernel-hardening@...ts.openwall.com>
Subject: Re: [PATCHv3 06/11] asm-generic: mm_hooks: allow hooks to be
overridden individually
On Tue, Apr 17, 2018 at 09:56:02PM +0200, Arnd Bergmann wrote:
> On Tue, Apr 17, 2018 at 8:37 PM, Mark Rutland <mark.rutland@....com> wrote:
> > Currently, an architecture must either implement all of the mm hooks
> > itself, or use all of those provided by the asm-generic implementation.
> > When an architecture only needs to override a single hook, it must copy
> > the stub implementations from the asm-generic version.
> >
> > To avoid this repetition, allow each hook to be overridden indiviually,
> > by placing each under an #ifndef block. As architectures providing their
> > own hooks can't include this file today, this shouldn't adversely affect
> > any existing hooks.
> >
> > Signed-off-by: Mark Rutland <mark.rutland@....com>
> > Cc: Arnd Bergmann <arnd@...db.de>
> > Cc: linux-arch@...r.kernel.org
>
> Acked-by: Arnd Bergmann <arnd@...db.de>
Cheers!
Mark.
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
