From: Suzuki Kuruppassery Poulose <suzuki.poulose@arm.com>
To: Will Deacon <will@kernel.org>, broonie@kernel.org
Cc: Catalin Marinas <catalin.marinas@arm.com>,
kernel-team@android.com, linux-arm-kernel@lists.infradead.org,
Marc Zyngier <maz@kernel.org>
Subject: Re: [PATCH 0/2] A couple of cleanups on top of for-next/e0pd
Date: Wed, 15 Jan 2020 16:47:42 +0000 [thread overview]
Message-ID: <0550689a-72b2-fe13-044c-a671eda8bb96@arm.com> (raw)
In-Reply-To: <20200115142900.28976-1-will@kernel.org>
On 15/01/2020 14:28, Will Deacon wrote:
> Hi Mark,
>
> I've queued the E0PD patches for 5.6 (thanks!), but in reading them a
> final time I noticed a couple of cleanups that I think we can make to
> kaslr_requires_kpti(). I don't have a TX1 to test them on, but I think
> the logic is sound.
>
> Please take a look, as I'd like to queue these on top.
>
> Thanks.
>
> Will
>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Suzuki K Poulose <suzuki.poulose@arm.com>
> Cc: Marc Zyngier <maz@kernel.org>
Looks good to me.
Acked-by: Suzuki K Poulose <suzuki.poulose@arm.com>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-01-15 16:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 14:28 [PATCH 0/2] A couple of cleanups on top of for-next/e0pd Will Deacon
2020-01-15 14:28 ` [PATCH 1/2] arm64: Simplify early check for broken TX1 when KASLR is enabled Will Deacon
2020-01-15 14:29 ` [PATCH 2/2] arm64: Use register field helper in kaslr_requires_kpti() Will Deacon
2020-01-15 17:06 ` Mark Brown
2020-01-15 15:11 ` [PATCH 0/2] A couple of cleanups on top of for-next/e0pd Catalin Marinas
2020-01-15 16:47 ` Suzuki Kuruppassery Poulose [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=0550689a-72b2-fe13-044c-a671eda8bb96@arm.com \
--to=suzuki.poulose@arm.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maz@kernel.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).