[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.9999.1906231045280.13854@viisi.sifive.com>
Date: Sun, 23 Jun 2019 10:51:33 -0700 (PDT)
From: Paul Walmsley <paul.walmsley@...ive.com>
To: Atish Patra <Atish.Patra@....com>, linux@...linux.org.uk
cc: "robh+dt@...nel.org" <robh+dt@...nel.org>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
"rfontana@...hat.com" <rfontana@...hat.com>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"davem@...emloft.net" <davem@...emloft.net>,
"jhugo@...eaurora.org" <jhugo@...eaurora.org>,
"aou@...s.berkeley.edu" <aou@...s.berkeley.edu>,
"mingo@...nel.org" <mingo@...nel.org>,
"catalin.marinas@....com" <catalin.marinas@....com>,
"mchehab+samsung@...nel.org" <mchehab+samsung@...nel.org>,
"Jonathan.Cameron@...wei.com" <Jonathan.Cameron@...wei.com>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linus.walleij@...aro.org" <linus.walleij@...aro.org>,
"will.deacon@....com" <will.deacon@....com>,
"morten.rasmussen@....com" <morten.rasmussen@....com>,
"mark.rutland@....com" <mark.rutland@....com>,
"palmer@...ive.com" <palmer@...ive.com>,
"peterz@...radead.org" <peterz@...radead.org>,
"ottosabart@...erm.com" <ottosabart@...erm.com>,
"sudeep.holla@....com" <sudeep.holla@....com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"rafael@...nel.org" <rafael@...nel.org>,
"anup@...infault.org" <anup@...infault.org>,
"linux@...linux.org.uk" <linux@...linux.org.uk>,
"linux-riscv@...ts.infradead.org" <linux-riscv@...ts.infradead.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v7 3/7] cpu-topology: Move cpu topology code to common
code.
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
Powered by blists - more mailing lists