From: Catalin Marinas <catalin.marinas@arm.com>
To: Gavin Shan <gshan@redhat.com>
Cc: mark.rutland@arm.com, lorenzo.pieralisi@arm.com,
robin.murphy@arm.com, shan.gavin@gmail.com, sudeep.holla@arm.com,
will@kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v5 0/4] arm64: Dereference CPU operations indirectly
Date: Tue, 24 Mar 2020 17:29:23 +0000 [thread overview]
Message-ID: <20200324172922.GG3901@mbp> (raw)
In-Reply-To: <20200318230145.72097-1-gshan@redhat.com>
On Thu, Mar 19, 2020 at 10:01:41AM +1100, Gavin Shan wrote:
> Gavin Shan (4):
> arm64: Declare ACPI parking protocol CPU operation if needed
> arm64: Rename cpu_read_ops() to init_cpu_ops()
> arm64: Introduce get_cpu_ops() helper function
> arm64: Remove CPU operations dereferencing array
I queued the first 3 patches for 5.7, they are useful on their own as a
code clean-up. I'll wait for the debate with Mark to settle on the last
patch.
Thanks.
--
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:[~2020-03-24 17:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 23:01 [PATCH v5 0/4] arm64: Dereference CPU operations indirectly Gavin Shan
2020-03-18 23:01 ` [PATCH v5 1/4] arm64: Declare ACPI parking protocol CPU operation if needed Gavin Shan
2020-03-18 23:01 ` [PATCH v5 2/4] arm64: Rename cpu_read_ops() to init_cpu_ops() Gavin Shan
2020-03-18 23:01 ` [PATCH v5 3/4] arm64: Introduce get_cpu_ops() helper function Gavin Shan
2020-03-19 19:31 ` Mark Rutland
2020-03-18 23:01 ` [PATCH v5 4/4] arm64: Remove CPU operations dereferencing array Gavin Shan
2020-03-19 19:38 ` Mark Rutland
2020-03-19 22:54 ` Gavin Shan
2020-03-24 17:29 ` Catalin Marinas [this message]
2020-03-25 11:49 ` [PATCH v5 0/4] arm64: Dereference CPU operations indirectly Gavin Shan
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=20200324172922.GG3901@mbp \
--to=catalin.marinas@arm.com \
--cc=gshan@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=mark.rutland@arm.com \
--cc=robin.murphy@arm.com \
--cc=shan.gavin@gmail.com \
--cc=sudeep.holla@arm.com \
--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).