From: Sudeep Holla <sudeep.holla@arm.com>
To: Russell King <linux@armlinux.org.uk>
Cc: linux-kernel@vger.kernel.org, Albert Ou <aou@eecs.berkeley.edu>,
Anup Patel <anup@brainfault.org>,
Catalin Marinas <catalin.marinas@arm.com>,
"David S. Miller" <davem@davemloft.net>,
devicetree@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Ingo Molnar <mingo@kernel.org>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Linus Walleij <linus.walleij@linaro.org>,
linux-riscv@lists.infradead.org,
Mark Rutland <mark.rutland@arm.com>,
Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
Morten Rasmussen <morten.rasmussen@arm.com>,
Otto Sabart <ottosabart@seberm.com>,
Palmer Dabbelt <palmer@sifive.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Richard Fontana <rfontana@redhat.com>,
Rob Herring <robh+dt@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Will Deacon <will.deacon@arm.com>,
Atish Patra <atish.patra@wdc.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v7 4/7] arm: Use common cpu_topology structure and functions.
Date: Mon, 24 Jun 2019 16:06:58 +0100 [thread overview]
Message-ID: <20190624150658.GA1623@e107155-lin> (raw)
In-Reply-To: <20190619121057.GE1360@e107155-lin>
On Wed, Jun 19, 2019 at 01:10:57PM +0100, Sudeep Holla wrote:
> Hi Russell,
>
> On Mon, Jun 17, 2019 at 11:59:17AM -0700, Atish Patra wrote:
> > Currently, ARM32 and ARM64 uses different data structures to represent
> > their cpu topologies. Since, we are moving the ARM64 topology to common
> > code to be used by other architectures, we can reuse that for ARM32 as
> > well.
> >
> > Take this opprtunity to remove the redundant functions from ARM32 and
> > reuse the common code instead.
> >
> > To: Russell King <linux@armlinux.org.uk>
> > Signed-off-by: Atish Patra <atish.patra@wdc.com>
> > Tested-by: Sudeep Holla <sudeep.holla@arm.com> (on TC2)
> > Reviewed-by : Sudeep Holla <sudeep.holla@arm.com>
> >
> > ---
> > Hi Russell,
> > Can we get a ACK for this patch ? We are hoping that the entire
> > series can be merged at one go.
>
> It would be nice to get this in for v5.3 as it's almost there.
> Are you fine with these changes ?
>
Do you have any objections with this patch ? We plan to merge through
RISC-V tree, please let us know. It has been acked-by all the other
maintainers.
--
Regards,
Sudeep
next prev parent reply other threads:[~2019-06-24 15:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-17 18:59 [PATCH v7 0/7] Unify CPU topology across ARM & RISC-V Atish Patra
2019-06-17 18:59 ` [PATCH v7 1/7] Documentation: DT: arm: add support for sockets defining package boundaries Atish Patra
2019-06-27 0:31 ` Paul Walmsley
2019-06-27 2:18 ` Atish Patra
2019-06-27 19:58 ` Atish Patra
2019-06-17 18:59 ` [PATCH v7 2/7] dt-binding: cpu-topology: Move cpu-map to a common binding Atish Patra
2019-06-17 18:59 ` [PATCH v7 3/7] cpu-topology: Move cpu topology code to common code Atish Patra
2019-06-19 17:38 ` Greg Kroah-Hartman
2019-06-21 22:31 ` Atish Patra
2019-06-23 17:51 ` Paul Walmsley
2019-06-17 18:59 ` [PATCH v7 4/7] arm: Use common cpu_topology structure and functions Atish Patra
2019-06-19 12:10 ` Sudeep Holla
2019-06-24 15:06 ` Sudeep Holla [this message]
2019-06-24 15:30 ` Russell King - ARM Linux admin
2019-06-24 15:33 ` Sudeep Holla
2019-06-17 18:59 ` [PATCH v7 5/7] RISC-V: Parse cpu topology during boot Atish Patra
2019-06-17 18:59 ` [PATCH v7 6/7] base: arch_topology: update Kconfig help description Atish Patra
2019-06-17 18:59 ` [PATCH v7 7/7] MAINTAINERS: Add an entry for generic architecture topology Atish Patra
2019-06-19 17:37 ` Greg Kroah-Hartman
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=20190624150658.GA1623@e107155-lin \
--to=sudeep.holla@arm.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=atish.patra@wdc.com \
--cc=catalin.marinas@arm.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=mchehab+samsung@kernel.org \
--cc=mingo@kernel.org \
--cc=morten.rasmussen@arm.com \
--cc=ottosabart@seberm.com \
--cc=palmer@sifive.com \
--cc=paul.walmsley@sifive.com \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=rfontana@redhat.com \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.de \
--cc=will.deacon@arm.com \
/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).