From: Rob Herring <robh@kernel.org>
To: Atish Patra <atish.patra@wdc.com>
Cc: linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
anup@brainfault.org, Damien.LeMoal@wdc.com,
linux-arm-kernel@lists.infradead.org, mark.rutland@arm.com,
sudeep.holla@arm.com, palmer@sifive.com,
devicetree@vger.kernel.org, juri.lelli@arm.com,
mick@ics.forth.gr, jeremy.linton@arm.com
Subject: Re: [RFC 1/3] dt-binding: cpu-topology: Move cpu-map to a common binding.
Date: Sat, 17 Nov 2018 10:32:53 -0600 [thread overview]
Message-ID: <20181117163253.GA6713@bogus> (raw)
In-Reply-To: <1541728209-3224-2-git-send-email-atish.patra@wdc.com>
On Thu, Nov 08, 2018 at 05:50:07PM -0800, Atish Patra wrote:
> cpu-map binding can be used to described cpu topology for both
> RISC-V & ARM. It makes more sense to move the binding to document
> to a common place.
>
> The relevant discussion can be found here.
> https://lkml.org/lkml/2018/11/6/19
>
> Signed-off-by: Atish Patra <atish.patra@wdc.com>
> ---
> Documentation/devicetree/bindings/arm/topology.txt | 475 -------------------
> .../devicetree/bindings/cpu/cpu-topology.txt | 526 +++++++++++++++++++++
> 2 files changed, 526 insertions(+), 475 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/arm/topology.txt
> create mode 100644 Documentation/devicetree/bindings/cpu/cpu-topology.txt
Please send this with '-M' option so we just get the real changes.
Rob
WARNING: multiple messages have this Message-ID (diff)
From: robh@kernel.org (Rob Herring)
To: linux-riscv@lists.infradead.org
Subject: [RFC 1/3] dt-binding: cpu-topology: Move cpu-map to a common binding.
Date: Sat, 17 Nov 2018 10:32:53 -0600 [thread overview]
Message-ID: <20181117163253.GA6713@bogus> (raw)
In-Reply-To: <1541728209-3224-2-git-send-email-atish.patra@wdc.com>
On Thu, Nov 08, 2018 at 05:50:07PM -0800, Atish Patra wrote:
> cpu-map binding can be used to described cpu topology for both
> RISC-V & ARM. It makes more sense to move the binding to document
> to a common place.
>
> The relevant discussion can be found here.
> https://lkml.org/lkml/2018/11/6/19
>
> Signed-off-by: Atish Patra <atish.patra@wdc.com>
> ---
> Documentation/devicetree/bindings/arm/topology.txt | 475 -------------------
> .../devicetree/bindings/cpu/cpu-topology.txt | 526 +++++++++++++++++++++
> 2 files changed, 526 insertions(+), 475 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/arm/topology.txt
> create mode 100644 Documentation/devicetree/bindings/cpu/cpu-topology.txt
Please send this with '-M' option so we just get the real changes.
Rob
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Atish Patra <atish.patra@wdc.com>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
Damien.LeMoal@wdc.com, juri.lelli@arm.com, anup@brainfault.org,
palmer@sifive.com, linux-kernel@vger.kernel.org,
jeremy.linton@arm.com, sudeep.holla@arm.com, mick@ics.forth.gr,
linux-riscv@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC 1/3] dt-binding: cpu-topology: Move cpu-map to a common binding.
Date: Sat, 17 Nov 2018 10:32:53 -0600 [thread overview]
Message-ID: <20181117163253.GA6713@bogus> (raw)
Message-ID: <20181117163253.lhBqUyRl_bMc7CRhN1jtYh_Hfs1tw5WHMVGtAJhp23s@z> (raw)
In-Reply-To: <1541728209-3224-2-git-send-email-atish.patra@wdc.com>
On Thu, Nov 08, 2018 at 05:50:07PM -0800, Atish Patra wrote:
> cpu-map binding can be used to described cpu topology for both
> RISC-V & ARM. It makes more sense to move the binding to document
> to a common place.
>
> The relevant discussion can be found here.
> https://lkml.org/lkml/2018/11/6/19
>
> Signed-off-by: Atish Patra <atish.patra@wdc.com>
> ---
> Documentation/devicetree/bindings/arm/topology.txt | 475 -------------------
> .../devicetree/bindings/cpu/cpu-topology.txt | 526 +++++++++++++++++++++
> 2 files changed, 526 insertions(+), 475 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/arm/topology.txt
> create mode 100644 Documentation/devicetree/bindings/cpu/cpu-topology.txt
Please send this with '-M' option so we just get the real changes.
Rob
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: robh@kernel.org (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC 1/3] dt-binding: cpu-topology: Move cpu-map to a common binding.
Date: Sat, 17 Nov 2018 10:32:53 -0600 [thread overview]
Message-ID: <20181117163253.GA6713@bogus> (raw)
In-Reply-To: <1541728209-3224-2-git-send-email-atish.patra@wdc.com>
On Thu, Nov 08, 2018 at 05:50:07PM -0800, Atish Patra wrote:
> cpu-map binding can be used to described cpu topology for both
> RISC-V & ARM. It makes more sense to move the binding to document
> to a common place.
>
> The relevant discussion can be found here.
> https://lkml.org/lkml/2018/11/6/19
>
> Signed-off-by: Atish Patra <atish.patra@wdc.com>
> ---
> Documentation/devicetree/bindings/arm/topology.txt | 475 -------------------
> .../devicetree/bindings/cpu/cpu-topology.txt | 526 +++++++++++++++++++++
> 2 files changed, 526 insertions(+), 475 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/arm/topology.txt
> create mode 100644 Documentation/devicetree/bindings/cpu/cpu-topology.txt
Please send this with '-M' option so we just get the real changes.
Rob
next prev parent reply other threads:[~2018-11-17 16:32 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-09 1:50 [RFC 0/3] Unify CPU topology across ARM64 & RISC-V Atish Patra
2018-11-09 1:50 ` Atish Patra
2018-11-09 1:50 ` Atish Patra
2018-11-09 1:50 ` Atish Patra
2018-11-09 1:50 ` [RFC 1/3] dt-binding: cpu-topology: Move cpu-map to a common binding Atish Patra
2018-11-09 1:50 ` Atish Patra
2018-11-09 1:50 ` Atish Patra
2018-11-09 1:50 ` Atish Patra
2018-11-17 16:32 ` Rob Herring [this message]
2018-11-17 16:32 ` Rob Herring
2018-11-17 16:32 ` Rob Herring
2018-11-17 16:32 ` Rob Herring
2018-11-19 17:57 ` Atish Patra
2018-11-19 17:57 ` Atish Patra
2018-11-19 17:57 ` Atish Patra
2018-11-19 17:57 ` Atish Patra
2018-11-19 17:57 ` Atish Patra
2018-11-09 1:50 ` [RFC 2/3] cpu-topology: Move cpu topology code to common code Atish Patra
2018-11-09 1:50 ` Atish Patra
2018-11-09 1:50 ` Atish Patra
2018-11-09 1:50 ` Atish Patra
2018-11-09 1:50 ` [RFC 3/3] RISC-V: Parse cpu topology during boot Atish Patra
2018-11-09 1:50 ` Atish Patra
2018-11-09 1:50 ` Atish Patra
2018-11-09 1:50 ` Atish Patra
2018-11-15 18:31 ` [RFC 0/3] Unify CPU topology across ARM64 & RISC-V Jeffrey Hugo
2018-11-15 18:31 ` Jeffrey Hugo
2018-11-15 18:31 ` Jeffrey Hugo
2018-11-15 18:31 ` Jeffrey Hugo
2018-11-19 17:46 ` Atish Patra
2018-11-19 17:46 ` Atish Patra
2018-11-19 17:46 ` Atish Patra
2018-11-19 17:46 ` Atish Patra
2018-11-19 17:46 ` Atish Patra
2018-11-20 11:11 ` Sudeep Holla
2018-11-20 11:11 ` Sudeep Holla
2018-11-20 11:11 ` Sudeep Holla
2018-11-20 11:11 ` Sudeep Holla
2018-11-20 15:28 ` Jeffrey Hugo
2018-11-20 15:28 ` Jeffrey Hugo
2018-11-20 15:28 ` Jeffrey Hugo
2018-11-20 15:28 ` Jeffrey Hugo
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=20181117163253.GA6713@bogus \
--to=robh@kernel.org \
--cc=Damien.LeMoal@wdc.com \
--cc=anup@brainfault.org \
--cc=atish.patra@wdc.com \
--cc=devicetree@vger.kernel.org \
--cc=jeremy.linton@arm.com \
--cc=juri.lelli@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=mick@ics.forth.gr \
--cc=palmer@sifive.com \
--cc=sudeep.holla@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.