From: Sudeep Holla <sudeep.holla@arm.com>
To: Atish Patra <atish.patra@wdc.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Albert Ou <aou@eecs.berkeley.edu>,
Anup Patel <anup@brainfault.org>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Catalin Marinas <catalin.marinas@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Dmitriy Cherkasov <dmitriy@oss-tech.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Ingo Molnar <mingo@kernel.org>,
Jeremy Linton <jeremy.linton@arm.com>,
Johan Hovold <johan@kernel.org>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>,
Mark Rutland <mark.rutland@arm.com>,
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>,
Rob Herring <robh+dt@kernel.org>,
Will Deacon <will.deacon@arm.com>,
Sudeep Holla <sudeep.holla@arm.com>
Subject: Re: [RFT/RFC PATCH v3 0/5] Unify CPU topology across ARM & RISC-V
Date: Fri, 12 Apr 2019 18:27:52 +0100 [thread overview]
Message-ID: <20190412172401.GA21340@e107155-lin> (raw)
In-Reply-To: <12c9f8b0-cdeb-2b9c-5662-6c5a08cd0a95@wdc.com>
On Wed, Apr 10, 2019 at 03:49:54PM -0700, Atish Patra wrote:
[...]
>
> Ping?
>
Sorry for the delay(was off for a while), will take a look next week.
> Specifically, patch 3 & 4 affects ARM & ARM64. Any tests on real hardware
> would be great.
>
Sure.
--
Regards,
Sudeep
WARNING: multiple messages have this Message-ID (diff)
From: Sudeep Holla <sudeep.holla@arm.com>
To: Atish Patra <atish.patra@wdc.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Albert Ou <aou@eecs.berkeley.edu>,
Anup Patel <anup@brainfault.org>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Catalin Marinas <catalin.marinas@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Dmitriy Cherkasov <dmitriy@oss-tech.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Ingo Molnar <mingo@kernel.org>,
Jeremy Linton <jeremy.linton@arm.com>,
Johan Hovold <johan@kernel.org>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>,
Mark Rutland <mark.rutland@arm.com>,
Morten Rasmussen <morten.rasmussen@arm.com>,
Otto Sabart <ottosabart@seberm.com>,
Palmer Dabbelt <palmer@sifive.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Peter Zijlstra (Inte
Subject: Re: [RFT/RFC PATCH v3 0/5] Unify CPU topology across ARM & RISC-V
Date: Fri, 12 Apr 2019 18:27:52 +0100 [thread overview]
Message-ID: <20190412172401.GA21340@e107155-lin> (raw)
In-Reply-To: <12c9f8b0-cdeb-2b9c-5662-6c5a08cd0a95@wdc.com>
On Wed, Apr 10, 2019 at 03:49:54PM -0700, Atish Patra wrote:
[...]
>
> Ping?
>
Sorry for the delay(was off for a while), will take a look next week.
> Specifically, patch 3 & 4 affects ARM & ARM64. Any tests on real hardware
> would be great.
>
Sure.
--
Regards,
Sudeep
WARNING: multiple messages have this Message-ID (diff)
From: Sudeep Holla <sudeep.holla@arm.com>
To: Atish Patra <atish.patra@wdc.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Peter Zijlstra \(Intel\)" <peterz@infradead.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Palmer Dabbelt <palmer@sifive.com>,
Will Deacon <will.deacon@arm.com>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>, Ingo Molnar <mingo@kernel.org>,
Dmitriy Cherkasov <dmitriy@oss-tech.org>,
Anup Patel <anup@brainfault.org>,
Morten Rasmussen <morten.rasmussen@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Albert Ou <aou@eecs.berkeley.edu>,
Johan Hovold <johan@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jeremy Linton <jeremy.linton@arm.com>,
Otto Sabart <ottosabart@seberm.com>,
Sudeep Holla <sudeep.holla@arm.com>
Subject: Re: [RFT/RFC PATCH v3 0/5] Unify CPU topology across ARM & RISC-V
Date: Fri, 12 Apr 2019 18:27:52 +0100 [thread overview]
Message-ID: <20190412172401.GA21340@e107155-lin> (raw)
In-Reply-To: <12c9f8b0-cdeb-2b9c-5662-6c5a08cd0a95@wdc.com>
On Wed, Apr 10, 2019 at 03:49:54PM -0700, Atish Patra wrote:
[...]
>
> Ping?
>
Sorry for the delay(was off for a while), will take a look next week.
> Specifically, patch 3 & 4 affects ARM & ARM64. Any tests on real hardware
> would be great.
>
Sure.
--
Regards,
Sudeep
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2019-04-12 17:28 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-20 23:48 [RFT/RFC PATCH v3 0/5] Unify CPU topology across ARM & RISC-V Atish Patra
2019-03-20 23:48 ` Atish Patra
2019-03-20 23:48 ` Atish Patra
2019-03-20 23:48 ` [RFT/RFC PATCH v3 1/5] Documentation: DT: arm: add support for sockets defining package boundaries Atish Patra
2019-03-20 23:48 ` Atish Patra
2019-03-20 23:48 ` Atish Patra
2019-03-20 23:48 ` [RFT/RFC PATCH v3 2/5] dt-binding: cpu-topology: Move cpu-map to a common binding Atish Patra
2019-03-20 23:48 ` Atish Patra
2019-03-20 23:48 ` Atish Patra
2019-03-24 21:16 ` Rob Herring
2019-03-24 21:16 ` Rob Herring
2019-03-24 21:16 ` Rob Herring
2019-03-20 23:48 ` [RFT/RFC PATCH v3 3/5] cpu-topology: Move cpu topology code to common code Atish Patra
2019-03-20 23:48 ` Atish Patra
2019-03-20 23:48 ` Atish Patra
2019-04-15 15:27 ` Sudeep Holla
2019-04-15 15:27 ` Sudeep Holla
2019-04-15 15:27 ` Sudeep Holla
2019-04-15 22:08 ` Atish Patra
2019-04-15 22:08 ` Atish Patra
2019-04-15 22:08 ` Atish Patra
2019-04-16 13:23 ` Sudeep Holla
2019-04-16 13:23 ` Sudeep Holla
2019-04-16 13:23 ` Sudeep Holla
2019-04-16 18:54 ` Atish Patra
2019-04-16 18:54 ` Atish Patra
2019-04-16 18:54 ` Atish Patra
2019-03-20 23:48 ` [RFT/RFC PATCH v3 4/5] arm: Use common cpu_topology Atish Patra
2019-03-20 23:48 ` Atish Patra
2019-03-20 23:48 ` Atish Patra
2019-04-15 15:31 ` Sudeep Holla
2019-04-15 15:31 ` Sudeep Holla
2019-04-15 15:31 ` Sudeep Holla
2019-04-15 21:16 ` Atish Patra
2019-04-15 21:16 ` Atish Patra
2019-04-15 21:16 ` Atish Patra
2019-04-16 13:09 ` Sudeep Holla
2019-04-16 13:09 ` Sudeep Holla
2019-04-16 13:09 ` Sudeep Holla
2019-04-16 19:04 ` Atish Patra
2019-04-16 19:04 ` Atish Patra
2019-04-16 19:04 ` Atish Patra
2019-03-20 23:48 ` [RFT/RFC PATCH v3 5/5] RISC-V: Parse cpu topology during boot Atish Patra
2019-03-20 23:48 ` Atish Patra
2019-03-20 23:48 ` Atish Patra
2019-04-10 22:49 ` [RFT/RFC PATCH v3 0/5] Unify CPU topology across ARM & RISC-V Atish Patra
2019-04-10 22:49 ` Atish Patra
2019-04-10 22:49 ` Atish Patra
2019-04-12 17:27 ` Sudeep Holla [this message]
2019-04-12 17:27 ` Sudeep Holla
2019-04-12 17:27 ` Sudeep Holla
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=20190412172401.GA21340@e107155-lin \
--to=sudeep.holla@arm.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=ard.biesheuvel@linaro.org \
--cc=atish.patra@wdc.com \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitriy@oss-tech.org \
--cc=gregkh@linuxfoundation.org \
--cc=jeremy.linton@arm.com \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mark.rutland@arm.com \
--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=robh+dt@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.