From: Catalin Marinas <catalin.marinas@arm.com>
To: Mark Brown <broonie@kernel.org>
Cc: Will Deacon <will@kernel.org>, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 4/4] arm64: Use a variable to store non-global mappings decision
Date: Wed, 30 Oct 2019 14:17:32 +0000 [thread overview]
Message-ID: <20191030141732.GA13309@arrakis.emea.arm.com> (raw)
In-Reply-To: <20191030124153.GB7218@sirena.co.uk>
On Wed, Oct 30, 2019 at 12:41:53PM +0000, Mark Brown wrote:
> BTW it'd be rather helpful to get patch 1 applied due to the constant
> conflicts in cpufeature.h, it's safe by itself.
Since we moved to using topic for-next/* branches, usually based on
-rc3, I'd rather see patch series on top of the vanilla kernel. We can
handle the trivial conflicts.
Of course, if there is functional dependency, we can discuss which
branch to base it on but I'd avoid for-next/core as a base as that's
rather volatile.
--
Catalin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-10-30 14:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 21:42 [PATCH v4 0/4] E0PD support Mark Brown
2019-10-24 21:42 ` [PATCH v4 1/4] arm64: Add initial support for E0PD Mark Brown
2019-10-24 21:42 ` [PATCH v4 2/4] arm64: Factor out checks for KASLR in KPTI code into separate function Mark Brown
2019-10-24 21:42 ` [PATCH v4 3/4] arm64: Don't use KPTI where we have E0PD Mark Brown
2019-10-24 21:42 ` [PATCH v4 4/4] arm64: Use a variable to store non-global mappings decision Mark Brown
2019-10-30 12:13 ` Catalin Marinas
2019-10-30 12:41 ` Mark Brown
2019-10-30 14:17 ` Catalin Marinas [this message]
2019-10-31 8:18 ` Mark Brown
2019-10-31 10:18 ` Catalin Marinas
2019-10-31 10:35 ` Mark Brown
2019-11-04 17:20 ` Mark Brown
2019-10-30 12:26 ` [PATCH v4 0/4] E0PD support Catalin Marinas
2019-10-30 12:54 ` Mark Brown
2019-10-31 11:26 ` Will Deacon
2019-10-31 12:13 ` John Garry
2019-10-31 12:42 ` Will Deacon
2019-10-31 13:00 ` Mark Brown
2019-10-31 13:09 ` Will Deacon
2019-10-31 14:13 ` John Garry
2019-10-31 16:06 ` Ard Biesheuvel
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=20191030141732.GA13309@arrakis.emea.arm.com \
--to=catalin.marinas@arm.com \
--cc=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=will@kernel.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).