From: Paul Walmsley <paul.walmsley@sifive.com>
To: Atish Patra <Atish.Patra@wdc.com>, linux@armlinux.org.uk
Cc: "robh+dt@kernel.org" <robh+dt@kernel.org>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"rfontana@redhat.com" <rfontana@redhat.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"davem@davemloft.net" <davem@davemloft.net>,
"jhugo@codeaurora.org" <jhugo@codeaurora.org>,
"aou@eecs.berkeley.edu" <aou@eecs.berkeley.edu>,
"mingo@kernel.org" <mingo@kernel.org>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"mchehab+samsung@kernel.org" <mchehab+samsung@kernel.org>,
"Jonathan.Cameron@huawei.com" <Jonathan.Cameron@huawei.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linus.walleij@linaro.org" <linus.walleij@linaro.org>,
"will.deacon@arm.com" <will.deacon@arm.com>,
"morten.rasmussen@arm.com" <morten.rasmussen@arm.com>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"palmer@sifive.com" <palmer@sifive.com>,
"peterz@infradead.org" <peterz@infradead.org>,
"ottosabart@seberm.com" <ottosabart@seberm.com>,
"sudeep.holla@arm.com" <sudeep.holla@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"rafael@kernel.org" <rafael@kernel.org>,
"anup@brainfault.org" <anup@brainfault.org>,
"linux@armlinux.org.uk" <linux@armlinux.org.uk>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v7 3/7] cpu-topology: Move cpu topology code to common code.
Date: Sun, 23 Jun 2019 10:51:33 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.21.9999.1906231045280.13854@viisi.sifive.com> (raw)
In-Reply-To: <91559562f2958fa904b53e621e596d6216efa9fb.camel@wdc.com>
Hi Atish, Russell,
On Fri, 21 Jun 2019, Atish Patra wrote:
> On Wed, 2019-06-19 at 19:38 +0200, Greg Kroah-Hartman wrote:
> > On Mon, Jun 17, 2019 at 11:59:16AM -0700, Atish Patra wrote:
> > > Both RISC-V & ARM64 are using cpu-map device tree to describe
> > > their cpu topology. It's better to move the relevant code to
> > > a common place instead of duplicate code.
[ ... ]
> I guess Greg has acked the series assuming that it will go through some
> other tree. Can you take it through RISC-V tree ?
>
> Sorry for the confusion.
>
> Note: We are still waiting for RMK's ACK on arm patch before it can be
> sent as a PR.
I'm fine to take it through the RISC-V tree, once Russell acks the
arch/arm patch.
- Paul
next prev parent reply other threads:[~2019-06-23 17:51 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 [this message]
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
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=alpine.DEB.2.21.9999.1906231045280.13854@viisi.sifive.com \
--to=paul.walmsley@sifive.com \
--cc=Atish.Patra@wdc.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=catalin.marinas@arm.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jhugo@codeaurora.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=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=rfontana@redhat.com \
--cc=robh+dt@kernel.org \
--cc=sudeep.holla@arm.com \
--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).